User equipment, base station and method

ABSTRACT

A user equipment (UE) is described. The UE may comprise high-layer processing circuitry configured to acquire high-layer processing circuitry configured to acquire at least a first RRC parameter for indicating txConfig and a second RRC parameter for indicating whether or not a transform precoding indicator field is included in a DCI format, reception circuitry configured to receive the DCI format for scheduling of a PUSCH and transmission circuitry configured to transmit the PUSCH.

TECHNICAL FIELD

The present invention relates to a user equipment, a base station and amethod.

BACKGROUND

In the 3rd Generation Partnership Project (3GPP), a radio access methodand a radio network for cellular mobile communications (hereinafter,referred to as Long Term Evolution, or Evolved Universal TerrestrialRadio Access) have been studied. In LTE (Long Term Evolution), a basestation device is also referred to as an evolved NodeB (eNodeB), and aterminal device is also referred to as a User Equipment (UE). LTE is acellular communication system in which multiple areas are deployed in acellular structure, with each of the multiple areas being covered by abase station device. A single base station device may manage multiplecells. Evolved Universal Terrestrial Radio Access is also referred asE-UTRA.

In the 3GPP, the next generation standard (New Radio: NR) has beenstudied in order to make a proposal to theInternational-Mobile-Telecommunication-2020 (IMT-2020) which is astandard for the next generation mobile communication system defined bythe International Telecommunications Union (ITU). NR has been expectedto satisfy a requirement considering three scenarios of enhanced MobileBroadBand (eMBB), massive Machine Type Communication (mMTC), and UltraReliable and Low Latency Communication (URLLC), in a single technologyframework.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram of a wireless communication systemaccording to an aspect of the present embodiment;

FIG. 2A and FIG. 2B are examples showing the relationship betweensubcarrier-spacing configuration u, the number of OFDM symbols per slotN^(slot) _(symb), and the CP configuration according to an aspect of thepresent embodiment;

FIG. 3 is a diagram showing an example of a method of configuring aresource grid according to an aspect of the present embodiment;

FIG. 4 is a diagram showing a configuration example of a resource grid3001 according to an aspect of the present embodiment;

FIG. 5 is a schematic block diagram showing a configuration example ofthe base station device 3 according to an aspect of the presentembodiment;

FIG. 6 is a schematic block diagram showing a configuration example ofthe terminal device 1 according to an aspect of the present embodiment;

FIG. 7 is a diagram showing a configuration example of an SS/PBCH blockaccording to an aspect of the present embodiment;

FIG. 8 is a diagram showing an example of the monitoring occasion of thesearch-space-set according to an aspect of the present embodiment;

FIG. 9 is an example configuration of a frame structure according to anaspect of the present embodiment;

FIG. 10 is an example configuration of a slot configuration according toan aspect of the present embodiment;

FIG. 11 is an example configuration of the baseband unit 13 in thewireless transmission unit 10 a according to an aspect of the presentembodiment;

FIG. 12 is an example configuration of Encoder 12000 according to anaspect of the present embodiment;

FIG. 13 is an example of the bit-selection procedure according to anaspect of the present embodiment;

FIG. 14 is an example of a circular buffer according to an aspect of thepresent embodiment;

FIG. 15 is an example configuration of a processing timeline accordingto an aspect of the present embodiment;

FIG. 16 is an example configuration of a processing timeline accordingto an aspect of the present embodiment;

FIG. 17 is an example configuration of a third type of PUSCHtransmission in multiple slots according to an aspect of the presentembodiment;

FIG. 18 is an example configuration of multiple instances in a thirdtype of PUSCH transmission in multiple slots according to an aspect ofthe present embodiment;

FIG. 19 is an example of a method for a UE;

FIG. 20 is an example of a method for a base station;

FIG. 21 is an example of an applicable PUSCH time domain resourceallocation for common search space and DCI format 0_0 in UE specificsearch space;

FIG. 22 is an example of an applicable PUSCH time domain resourceallocation for DCI format 0_1 in UE specific search space scrambled withC-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI;

FIG. 23 is an example of an applicable PUSCH time domain resourceallocation for DCI format 0_2 in UE specific search space scrambled withC-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI;

FIG. 24 is an example of a default PUSCH time domain resource allocationA for normal CP;

FIG. 25 is an example of a redundancy version for PUSCH transmission;

FIG. 26 is an example of a table used for the precoding information andnumber of layers field in the DCI format 0_1/0_2;

FIG. 27 is an example of a table used for the precoding information andnumber of layers field in the DCI format 0_1/0_2;

FIG. 28 is an example of a table used for the precoding information andnumber of layers field in the DCI format 0_1/0_2;

FIG. 29 is an example of a table used for the second precodinginformation field in the DCI format 0_1/0_2;

FIG. 30A and FIG. 30B are examples of a table used for the secondprecoding information field in the DCI format 0_1/0_2;

FIG. 31 is an example of a table used for the antenna ports field in theDCI format 0_1/0_2; and

FIG. 32 is an example of a table used for the antenna ports field in theDCI format 0_1/0_2.

DETAILED DESCRIPTION

A user equipment (UE) is described. The UE may comprise high-layerprocessing circuitry configured to acquire at least a first RRCparameter for indicating txConfig and a second RRC parameter forindicating whether or not a transform precoding indicator field isincluded in a DCI format, reception circuitry configured to receive theDCI format for scheduling of a PUSCH, and transmission circuitryconfigured to transmit the PUSCH scheduled by the DCI format, wherein ina case that the first RRC parameter indicates codebook and the secondRRC parameter indicates that the transform precoding indicator field isincluded in the DCI format, the reception circuitry is configured tomonitor the DCI format including a first DCI field with a maximum numberof bits among one or more tables applied based on values of a third RRCparameter, a fourth RRC parameter, a fifth RRC parameter, a sixth RRCparameter and a transform precoder.

A base station is described. The base station may comprise higher-layerprocessing circuitry configured to provide at least a first RRCparameter for indicating txConfig and a second RRC parameter forindicating whether or not a transform precoding indicator field isincluded in a DCI format, transmission circuitry configured to transmitthe DCI format for scheduling of a PUSCH, and reception circuitryconfigured to receive the PUSCH scheduled by the DCI format, wherein ina case that the first RRC parameter indicates disabled and the secondRRC parameter indicates that the transform precoding indicator field isincluded in the DCI format, the transmission circuitry is configured totransmit the DCI format including a first DCI field with a maximumnumber of bits among one or more tables applied based on values of athird RRC parameter, a fourth RRC parameter, a fifth RRC parameter, asixth RRC parameter and a transform precoder.

A method for a user equipment (UE) is described. The method may compriseacquiring at least a first RRC parameter for indicating txConfig and asecond RRC parameter for indicating whether or not a transform precodingindicator field is included in a DCI format, receiving the DCI formatfor scheduling of a PUSCH, and transmitting the PUSCH scheduled by theDCI format, wherein monitoring the DCI format including a first DCIfield with a maximum number of bits among one or more tables appliedbased on values of a third RRC parameter, a fourth RRC parameter, afifth RRC parameter, a sixth RRC parameter and a transform precoder in acase that the first RRC parameter indicates codebook and the second RRCparameter indicates that the transform precoding indicator field isincluded in the DCI format.

‘The available slot-based counting (PUSCH repetition counting) isconfigured’ may be referred to as ‘the slot-based counting (PUSCHrepetition counting) set to enabled is configured’ or ‘the slot-basedcounting (PUSCH repetition counting) is enabled’ or ‘an RRC parameterAvailableSlotCounting is enabled’.

‘The available slot-based counting (PUSCH repetition counting) is notconfigured’ may be referred to as ‘the slot-based counting (PUSCHrepetition counting) set to disabled is configured’ or ‘the slot-basedcounting (PUSCH repetition counting) is disabled’ or ‘an RRC parameterfor indicating the available slot-based counting (PUSCH repetitioncounting) is not configured’ or ‘an RRC parameter AvailableSlotCountingis disabled’.

floor (CX) may be a floor function for real number CX. For example,floor (CX) may be a function that provides the largest integer within arange that does not exceed the real number CX. ceil (DX) may be aceiling function to a real number DX. For example, ceil (DX) may be afunction that provides the smallest integer within the range not lessthan the real number DX. mod (EX, FX) may be a function that providesthe remainder obtained by dividing EX by FX. mod (EX, FX) may be afunction that provides a value which corresponds to the remainder ofdividing EX by FX. It is exp (GX)=e{circumflex over ( )}GX. Here, e isNapier number. (HX){circumflex over ( )}(IX) indicates IX to the powerof HX.

In a wireless communication system according to one aspect of thepresent embodiment, at least OFDM (Orthogonal Frequency DivisionMultiplex) is used. An OFDM symbol is a unit of time domain of the OFDM.The OFDM symbol includes at least one or more subcarriers. An OFDMsymbol is converted to a time-continuous signal in baseband signalgeneration. In downlink, at least CP-OFDM (Cyclic Prefix-OrthogonalFrequency Division Multiplex) is used. In uplink, either CP-OFDM orDFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal FrequencyDivision Multiplex) is used. DFT-s-OFDM may be given by applyingtransform precoding to CP-OFDM. CP-OFDM is OFDM using CP (CyclicPrefix).

Either DFT-s-OFDM or CP-OFDM may be given based whether or not transformprecoder (or transform precoding) is enabled. DFT-s-OFDM may be given ifthe transform precoder (or transform precoding) is enabled. CP-OFDM maybe given if the transform precoder (or transform precoding) is disabled.E.g. either enabled transform precoder or disabled transform precoderfor PUSCH may be indicated based on RRC parameters transformPrecoder inPUSCH-Config or ConfiguredGrantConfig and/or msg3-transformPrecoder inRACH-ConfigCommon.

The RRC parameter transformPrecoder indicates the UE specific selectionof the transform precoder for a PUSCH. If the transformPrecoder isabsent/not configured, the UE applies the value of themsg3-transformPrecoder to the transform precoder for the PUSCH.

The msg3-transformPrecoder indicates that the UE enables the transformprecoder for Msg3 transmission. If the msg3-transformPrecoder isprovided/configured, the UE enables the transform precoder for the Msg3transmission. If the msg3-transformPrecoder is absent/not configured/notprovided, the UE disables the transform precoder for Msg3 transmission.

The OFDM symbol may be a designation including a CP added to the OFDMsymbol. That is, an OFDM symbol may be configured to include the OFDMsymbol and a CP added to the OFDM symbol.

FIG. 1 is a conceptual diagram of a wireless communication systemaccording to an aspect of the present embodiment. In FIG. 1 , thewireless communication system includes at least terminal device 1A to 1Cand a base station device 3 (BS #3: Base station #3). Hereinafter, theterminal devices 1A to 1C are also referred to as a terminal device 1(UE #1: User Equipment #1).

The base station device 3 may be configured to include one or moretransmission devices (or transmission points, transmission devices,reception devices, transmission points, reception points). When the basestation device 3 is configured by a plurality of transmission devices,each of the plurality of transmission devices may be arranged at adifferent position.

The base station device 3 may provide one or more serving cells. Aserving cell may be defined as a set of resources used for wirelesscommunication. A serving cell is also referred to as a cell.

A serving cell may be configured to include at least one downlinkcomponent carrier (downlink carrier) and/or one uplink component carrier(uplink carrier). A serving cell may be configured to include at leasttwo or more downlink component carriers and/or two or more uplinkcomponent carriers. A downlink component carrier and an uplink componentcarrier are also referred to as component carriers (carriers).

For example, one resource grid may be provided for one componentcarrier. For example, one resource grid may be provided for onecomponent carrier and a subcarrier-spacing configuration u. Asubcarrier-spacing configuration u is also referred to as numerology. Aresource grid includes N^(size,u) _(grid,x)N^(RB) _(sc) subcarriers. Theresource grid starts from a common resource block with index N^(size,u)_(grid). The common resource block with the index N^(start,u) _(grid) isalso referred to as a reference point of the resource grid. The resourcegrid includes N^(subframe,u) _(symb) OFDM symbols. The subscript xindicates the transmission direction and indicates either downlink oruplink. One resource grid is provided for an antenna port p, asubcarrier-spacing configuration u, and a transmission direction x.

Resource grid is also referred to as carrier.

N^(size,u) _(grid,x) and N^(start,u) _(grid) are given based at least onan RRC parameter (e.g. referred to as RRC parameter CarrierBandwidth).The RRC parameter is used to define one or more SCS (SubCarrier-Spacing)specific carriers. One resource grid corresponds to one SCS specificcarrier. One component carrier may comprise one or more SCS specificcarriers. The SCS specific carrier may be included in a systeminformation block (SIB). For each SCS specific carrier, asubcarrier-spacing configuration u may be provided.

FIG. 2A and FIG. 2B are examples showing the relationship betweensubcarrier-spacing configuration u, the number of OFDM symbols per slotN^(slot) _(symb), and the CP configuration according to an aspect of thepresent embodiment. In FIG. 2A, for example, when the subcarrier-spacingconfiguration u is set to 2 and the CP configuration is set to normal CP(normal cyclic prefix), N^(slot) _(symb)=14, N^(frame,u) _(slot)=40,N^(subframe,u) _(slot)=4. Further, in FIG. 2B, for example, when thesubcarrier-spacing configuration u is set to 2 and the CP configurationis set to an extended CP (extended cyclic prefix), N^(slot) _(symb)=12,N^(frame,u) _(slot)=40, N^(subframe,u) _(slot)=4.

In the wireless communication system according to an aspect of thepresent embodiment, a time unit T, may be used to represent the lengthof the time domain. The time unit T_(c) is T_(c)=1/(df_(max)*N_(f)). Itis df_(max)=480 kHz. It is N_(f)=4096. The constant k isk=df_(max)*N_(f)/(df_(ref)N_(f,ref))=64. df_(ref) is 15 kHz. N_(f,ref)is 2048.

Transmission of signals in the downlink and/or transmission of signalsin the uplink may be organized into radio frames (system frames, frames)of length T_(f). It is T_(f)=(df_(max) N_(f)/100)*T_(s)=10 ms. One radioframe is configured to include ten subframes. The subframe length isT_(sf)=(df_(max)N_(f)/1000) T_(s)=1 ms. The number of OFDM symbols persubframe is N^(subframe,u) _(symb)=N^(subframe,u) _(slot).

For a subcarrier-spacing configuration u, the number of slots includedin a subframe and indexes may be given. For example, slot index n^(u)_(s,f) may be given in ascending order with an integer value rangingfrom 0 to N^(subframe,u) _(slot)−1 in a subframe. For subcarrier-spacingconfiguration u, the number of slots included in a radio frame andindexes of slots included in the radio frame may be given. Also, theslot index n^(u) _(s,f) may be given in ascending order with an integervalue ranging from 0 to N^(frame,u) _(slot)−1 in the radio frame.Consecutive N^(slot) _(symb) OFDM symbols may be included in one slot.It is N^(slot) _(symb)=14.

FIG. 3 is a diagram showing an example of a method of configuring aresource grid according to an aspect of the present embodiment. Thehorizontal axis in FIG. 3 indicates frequency domain. FIG. 3 shows aconfiguration example of a resource grid of subcarrier-spacingconfiguration u=u₁ in the component carrier 300 and a configurationexample of a resource grid of subcarrier-spacing configuration u=u₂ in acomponent carrier. One or more subcarrier-spacing configuration may beset for a component carrier. Although it is assumed in FIG. 3 thatu₁=u₂−1, various aspects of this embodiment are not limited to thecondition of u₁=u₂−1.

The component carrier 300 is a band having a predetermined width in thefrequency domain.

Point 3000 is an identifier for identifying a subcarrier. Point 3000 isalso referred to as point A. The common resource block (CRB) set 3100 isa set of common resource blocks for the subcarrier-spacing configurationu₁.

Among the common resource block-set 3100, the common resource blockincluding the point 3000 (the block indicated by the upper rightdiagonal line in FIG. 3 ) is also referred to as a reference point ofthe common resource block-set 3100. The reference point of the commonresource block-set 3100 may be a common resource block with index 0 inthe common resource block-set 3100.

The offset 3011 is an offset from the reference point of the commonresource block-set 3100 to the reference point of the resource grid3001. The offset 3011 is indicated by the number of common resourceblocks which is relative to the subcarrier-spacing configuration u₁. Theresource grid 3001 includes N^(size,u) _(grid,x) common resource blocksstarting from the reference point of the resource grid 3001.

The offset 3013 is an offset from the reference point of the resourcegrid 3001 to the reference point (N^(start,u) _(BWP,i1)) of the BWP(BandWidth Part) 3003 of the index i1.

Common resource block-set 3200 is a set of common resource blocks withrespect to subcarrier-spacing configuration u₂.

A common resource block including the point 3000 (a block indicated by aupper left diagonal line in FIG. 3 ) in the common resource block-set3200 is also referred to as a reference point of the common resourceblock-set 3200. The reference point of the common resource block-set3200 may be a common resource block with index 0 in the common resourceblock-set 3200.

The offset 3012 is an offset from the reference point of the commonresource block-set 3200 to the reference point of the resource grid3002. The offset 3012 is indicated by the number of common resourceblocks for subcarrier-spacing configuration u=u₂. The resource grid 3002includes N^(size,u) _(grid2,x) common resource blocks starting from thereference point of the resource grid 3002.

The offset 3014 is an offset from the reference point of the resourcegrid 3002 to the reference point (N^(start,u) _(BWP,i2)) of the BWP 3004with index i₂.

FIG. 4 is a diagram showing a configuration example of a resource grid3001 according to an aspect of the present embodiment. In the resourcegrid of FIG. 4 , the horizontal axis indicates OFDM symbol indexl_(sym), and the vertical axis indicates the subcarrier index k_(sc).The resource grid 3001 includes N^(size,u) _(grid,x)×N^(RB) _(sc)subcarriers, and includes N^(subframe,u) _(symb) OFDM symbols. Aresource specified by the subcarrier index k_(sc) and the OFDM symbolindex l_(sym) in a resource grid is also referred to as a resourceelement (RE).

A resource block (RB) includes N^(RB) _(sc) consecutive subcarriers. Aresource block is a generic name of a common resource block, a physicalresource block (PRB), and a virtual resource block (VRB). It is N^(RB)_(sc)=12.

A resource block unit is a set of resources that corresponds to one OFDMsymbol in one resource block. That is, one resource block unit includes12 resource elements which corresponds to one OFDM symbol in oneresource block.

Common resource blocks for a subcarrier-spacing configuration u areindexed in ascending order from 0 in the frequency domain in a commonresource block-set. The common resource block with index 0 for thesubcarrier-spacing configuration u includes (or collides with, matches)the point 3000. The index n^(u) _(CRB) of the common resource block withrespect to the subcarrier-spacing configuration u satisfies therelationship of n^(u) _(CRB)=ceil (k_(sc)/N^(RB) _(sc)). The subcarrierwith k_(sc)=0 is a subcarrier with the same center frequency as thecenter frequency of the subcarrier which corresponds to the point 3000.

Physical resource blocks for a subcarrier-spacing configuration u areindexed in ascending order from 0 in the frequency domain in a BWP. Theindex n^(u) _(PRB) of the physical resource block with respect to thesubcarrier-spacing configuration u satisfies the relationship of n^(u)_(CRB)=n^(u) _(PRB)+N^(start,u) _(BWP,i). The N^(start,u) _(BWP,i)indicates the reference point of BWP with index i.

A BWP is defined as a subset of common resource blocks included in theresource grid. The BWP includes N^(size,u) _(BWP,i) common resourceblocks starting from the reference points N^(start,u) _(BWP,i). A BWPfor the downlink component carrier is also referred to as a downlinkBWP. A BWP for the uplink component carrier is also referred to as anuplink BWP.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. For example, thechannel may correspond to a physical channel. For example, the symbolsmay correspond to OFDM symbols. For example, the symbols may correspondto resource block units. For example, the symbols may correspond toresource elements.

Two antenna ports are said to be QCL (Quasi Co-Located) if thelarge-scale properties of the channel over which a symbol on one antennaport is conveyed can be inferred from the channel over which a symbol onthe other antenna port is conveyed. The large-scale properties includeone or more of delay spread, Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters.

Carrier aggregation may be communication using a plurality of aggregatedserving cells. Carrier aggregation may be communication using aplurality of aggregated component carriers. Carrier aggregation may becommunication using a plurality of aggregated downlink componentcarriers. Carrier aggregation may be communication using a plurality ofaggregated uplink component carriers.

FIG. 5 is a schematic block diagram showing a configuration example ofthe base station device 3 according to an aspect of the presentembodiment. As shown in FIG. 5 , the base station device 3 includes atleast a part or all of the wireless transmission/reception unit(physical layer processing unit) 30 and the higher-layer processing unit34. The wireless transmission/reception unit 30 includes at least a partor all of the antenna unit 31, the RF unit 32 (Radio Frequency unit 32),and the baseband unit 33. The higher-layer processing unit 34 includesat least a part or all of the medium access control layer processingunit 35 and the radio resource control (RRC) layer processing unit 36.

The wireless transmission/reception unit 30 includes at least a part ofor all of a wireless transmission unit 30 a and a wireless receptionunit 30 b. The configuration of the baseband unit 33 included in thewireless transmission unit 30 a and the configuration of the basebandunit 33 included in the wireless reception unit 30 b may be the same ordifferent. The configuration of the RF unit 32 included in the wirelesstransmission unit 30 a and the configuration of the RF unit 32 includedin the wireless reception unit 30 b may be the same or different. Theconfiguration of the antenna unit 31 included in the wirelesstransmission unit 30 a and the configuration of the antenna unit 31included in the wireless reception unit 30 b may be the same ordifferent.

The higher-layer processing unit 34 provides downlink data (a transportblock) to the wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a). The higher-layer processing unit 34 performsprocessing of a medium access control (MAC) layer, a packet dataconvergence protocol layer (PDCP layer), a radio link control layer (RLClayer) and/or an RRC layer.

The medium access control layer processing unit 35 included in thehigher-layer processing unit 34 performs processing of the MAC layer.

The radio resource control layer processing unit 36 included in thehigher-layer processing unit 34 performs the process of the RRC layer.The radio resource control layer processing unit 36 manages variousconfiguration information/parameters (RRC parameters) of the terminaldevice 1. The radio resource control layer processing unit 36 configuresan RRC parameter based on the RRC message received from the terminaldevice 1.

The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) performs processing such as encoding andmodulation. The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) generates a physical signal by encoding andmodulating the downlink data. The wireless transmission/reception unit30 (or the wireless transmission unit 30 a) converts OFDM symbols in thephysical signal to a baseband signal by conversion to a time-continuoussignal. The wireless transmission/reception unit 30 (or the wirelesstransmission unit 30 a) transmits the baseband signal (or the physicalsignal) to the terminal device 1 via radio frequency. The wirelesstransmission/reception unit 30 (or the wireless transmission unit 30 a)may arrange the baseband signal (or the physical signal) on a componentcarrier and transmit the baseband signal (or the physical signal) to theterminal device 1.

The wireless transmission/reception unit 30 (or the wireless receptionunit 30 b) performs processing such as demodulation and decoding. Thewireless transmission/reception unit 30 (or the wireless reception unit30 b) separates, demodulates and decodes the received physical signal,and provides the decoded information to the higher-layer processing unit34. The wireless transmission/reception unit 30 (or the wirelessreception unit 30 b) may perform the channel access procedure prior tothe transmission of the physical signal.

The RF unit 32 demodulates the physical signal received via the antennaunit 31 into a baseband signal (down convert), and/or removes extrafrequency components. The RF unit 32 provides the processed analogsignal to the baseband unit 33.

The baseband unit 33 converts an analog signal (signals on radiofrequency) input from the RF unit 32 into a digital signal (a basebandsignal). The baseband unit 33 separates a portion which corresponds toCP (Cyclic Prefix) from the digital signal. The baseband unit 33performs Fast Fourier Transformation (FFT) on the digital signal fromwhich the CP has been removed. The baseband unit 33 provides thephysical signal in the frequency domain.

The baseband unit 33 performs Inverse Fast Fourier Transformation (IFFT)on downlink data to generate an OFDM symbol, adds a CP to the generatedOFDM symbol, generates a digital signal (baseband signal), and convertthe digital signal into an analog signal. The baseband unit 33 providesthe analog signal to the RF unit 32.

The RF unit 32 removes extra frequency components from the analog signal(signals on radio frequency) input from the baseband unit 33,up-converts the analog signal to a radio frequency and transmits it viathe antenna unit 31. The RF unit 32 may have a function of controllingtransmission power. The RF unit 32 is also referred to as a transmissionpower control unit.

At least one or more serving cells (or one or more component carriers,one or more downlink component carriers, one or more uplink componentcarriers) may be configured for the terminal device 1.

Each of the serving cells set for the terminal device 1 may be any ofPCell (Primary cell), PSCell (Primary SCG cell), and SCell (SecondaryCell).

A PCell is a serving cell included in a MCG (Master Cell Group). A PCellis a cell (implemented cell) which performs an initial connectionestablishment procedure or a connection re-establishment procedure bythe terminal device 1.

A PSCell is a serving cell included in a SCG (Secondary Cell Group). APSCell is a serving cell in which random-access is performed by theterminal device 1 in a reconfiguration procedure with synchronization(Reconfiguration with synchronization).

A SCell may be included in either a MCG or a SCG.

The serving cell group (cell group) is a designation including at leastMCG and SCG. The serving cell group may include one or more servingcells (or one or more component carriers). One or more serving cells (orone or more component carriers) included in the serving cell group maybe operated by carrier aggregation.

One or more downlink BWPs may be configured for each serving cell (oreach downlink component carrier). One or more uplink BWPs may beconfigured for each serving cell (or each uplink component carrier).

Among the one or more downlink BWPs set for the serving cell (or thedownlink component carrier), one downlink BWP may be set as an activedownlink BWP (or one downlink BWP may be activated). Among the one ormore uplink BWPs set for the serving cell (or the uplink componentcarrier), one uplink BWP may be set as an active uplink BWP (or oneuplink BWP may be activated).

A PDSCH, a PDCCH, and a CSI-RS may be received in the active downlinkBWP. The terminal device 1 may receive the PDSCH, the PDCCH, and theCSI-RS in the active downlink BWP. A PUCCH and a PUSCH may be sent onthe active uplink BWP. The terminal device 1 may transmit the PUCCH andthe PUSCH in the active uplink BWP. The active downlink BWP and theactive uplink BWP are also referred to as active BWP.

The PDSCH, the PDCCH, and the CSI-RS may not be received in downlinkBWPs (inactive downlink BWPs) other than the active downlink BWP. Theterminal device 1 may not receive the PDSCH, the PDCCH, and the CSI-RSin the downlink BWPs which are other than the active downlink BWP. ThePUCCH and the PUSCH do not need to be transmitted in uplink BWPs(inactive uplink BWPs) other than the active uplink BWP. The terminaldevice 1 may not transmit the PUCCH and the PUSCH in the uplink BWPswhich is other than the active uplink BWP. The inactive downlink BWP andthe inactive uplink BWP are also referred to as inactive BWP.

Downlink BWP switching deactivates an active downlink BWP and activatesone of inactive downlink BWPs which are other than the active downlinkBWP. The downlink BWP switching may be controlled by a BWP fieldincluded in a downlink control information. The downlink BWP switchingmay be controlled based on higher-layer parameters.

Uplink BWP switching is used to deactivate an active uplink BWP andactivate any inactive uplink BWP which is other than the active uplinkBWP. Uplink BWP switching may be controlled by a BWP field included in adownlink control information. The uplink BWP switching may be controlledbased on higher-layer parameters.

Among the one or more downlink BWPs set for the serving cell, two ormore downlink BWPs may not be set as active downlink BWPs. For theserving cell, one downlink BWP may be active at a certain time.

Among the one or more uplink BWPs set for the serving cell, two or moreuplink BWPs may not be set as active uplink BWPs. For the serving cell,one uplink BWP may be active at a certain time.

FIG. 6 is a schematic block diagram showing a configuration example ofthe terminal device 1 according to an aspect of the present embodiment.As shown in FIG. 6 , the terminal device 1 includes at least a part orall of the wireless transmission/reception unit (physical layerprocessing unit) 10 and the higher-layer processing unit 14. Thewireless transmission/reception unit 10 includes at least a part or allof the antenna unit 11, the RF unit 12, and the baseband unit 13. Thehigher-layer processing unit 14 includes at least a part or all of themedium access control layer processing unit 15 and the radio resourcecontrol layer processing unit 16.

The wireless transmission/reception unit 10 includes at least a part ofor all of a wireless transmission unit 10 a and a wireless receptionunit 10 b. The configuration of the baseband unit 13 included in thewireless transmission unit 10 a and the configuration of the basebandunit 13 included in the wireless reception unit 10 b may be the same ordifferent. The configuration of the RF unit 12 included in the wirelesstransmission unit 10 a and the RF unit 12 included in the wirelessreception unit 10 b may be the same or different. The configuration ofthe antenna unit 11 included in the wireless transmission unit 10 a andthe configuration of the antenna unit 11 included in the wirelessreception unit 10 b may be the same or different.

The higher-layer processing unit 14 provides uplink data (a transportblock) to the wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a). The higher-layer processing unit 14 performsprocessing of a MAC layer, a packet data integration protocol layer, aradio link control layer, and/or an RRC layer.

The medium access control layer processing unit 15 included in thehigher-layer processing unit 14 performs processing of the MAC layer.

The radio resource control layer processing unit 16 included in thehigher-layer processing unit 14 performs the process of the RRC layer.The radio resource control layer processing unit 16 manages variousconfiguration information/parameters (RRC parameters) of the terminaldevice 1. The radio resource control layer processing unit 16 configuresRRC parameters based on the RRC message received from the base stationdevice 3.

The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) performs processing such as encoding andmodulation. The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) generates a physical signal by encoding andmodulating the uplink data. The wireless transmission/reception unit 10(or the wireless transmission unit 10 a) converts OFDM symbols in thephysical signal to a baseband signal by conversion to a time-continuoussignal. The wireless transmission/reception unit 10 (or the wirelesstransmission unit 10 a) transmits the baseband signal (or the physicalsignal) to the base station device 3 via radio frequency. The wirelesstransmission/reception unit 10 (or the wireless transmission unit 10 a)may arrange the baseband signal (or the physical signal) on a BWP(active uplink BWP) and transmit the baseband signal (or the physicalsignal) to the base station device 3.

The wireless transmission/reception unit 10 (or the wireless receptionunit 10 b) performs processing such as demodulation and decoding. Thewireless transmission/reception unit 10 (or the wireless reception unit10 b) may receive a physical signal in a BWP (active downlink BWP) of aserving cell. The wireless transmission/reception unit 10 (or thewireless reception unit 10 b) separates, demodulates and decodes thereceived physical signal, and provides the decoded information to thehigher-layer processing unit 14. The wireless transmission/receptionunit 10 (or the wireless reception unit 10 b) may perform the channelaccess procedure prior to the transmission of the physical signal.

The RF unit 12 demodulates the physical signal received via the antennaunit 11 into a baseband signal (down convert), and/or removes extrafrequency components. The RF unit 12 provides the processed analogsignal to the baseband unit 13.

The baseband unit 13 converts an analog signal (signals on radiofrequency) input from the RF unit 12 into a digital signal (a basebandsignal). The baseband unit 13 separates a portion which corresponds toCP from the digital signal, performs fast Fourier transformation on thedigital signal from which the CP has been removed, and provides thephysical signal in the frequency domain.

The baseband unit 13 performs inverse fast Fourier transformation onuplink data to generate an OFDM symbol, adds a CP to the generated OFDMsymbol, generates a digital signal (baseband signal), and convert thedigital signal into an analog signal. The baseband unit 13 provides theanalog signal to the RF unit 12.

The RF unit 12 removes extra frequency components from the analog signal(signals on radio frequency) input from the baseband unit 13,up-converts the analog signal to a radio frequency, and transmits it viathe antenna unit 11 The RF unit 12 may have a function of controllingtransmission power. The RF unit 12 is also referred to as a transmissionpower control unit.

Hereinafter, physical signals (signals) will be described.

Physical signal is a generic term for downlink physical channels,downlink physical signals, uplink physical channels, and uplink physicalchannels. The physical channel is a generic term for downlink physicalchannels and uplink physical channels.

An uplink physical channel may correspond to a set of resource elementsthat carry information originating from the higher-layer and/or uplinkcontrol information. The uplink physical channel may be a physicalchannel used in an uplink component carrier. The uplink physical channelmay be transmitted by the terminal device 1. The uplink physical channelmay be received by the base station device 3. In the wirelesscommunication system according to one aspect of the present embodiment,at least part or all of PUCCH (Physical Uplink Control CHannel), PUSCH(Physical Uplink Shared CHannel), and PRACH (Physical Random AccessCHannel) may be used.

A PUCCH may be used to transmit uplink control information (UCI). ThePUCCH may be sent to deliver (transmission, convey) uplink controlinformation. The uplink control information may be mapped to (orarranged in) the PUCCH. The terminal device 1 may transmit PUCCH inwhich uplink control information is arranged. The base station device 3may receive the PUCCH in which the uplink control information isarranged.

Uplink control information (uplink control information bit, uplinkcontrol information sequence, uplink control information type) includesat least part or all of channel state information (CSI), schedulingrequest (SR), and HARQ-ACK (Hybrid Automatic Repeat reQuestACKnowledgement).

Channel state information is conveyed by using channel state informationbits or a channel state information sequence. Scheduling request is alsoreferred to as a scheduling request bit or a scheduling requestsequence. HARQ-ACK information is also referred to as a HARQ-ACKinformation bit or a HARQ-ACK information sequence.

HARQ-ACK information may include HARQ-ACK status which corresponds to atransport block (TB: Transport block, MAC PDU: Medium Access ControlProtocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH:Uplink-Shared Channel, PDSCH: Physical Downlink Shared CHannel, PUSCH:Physical Uplink Shared CHannel). The HARQ-ACK status may indicate ACK(acknowledgement) or NACK (negative-acknowledgement) corresponding tothe transport block. The ACK may indicate that the transport block hasbeen successfully decoded. The NACK may indicate that the transportblock has not been successfully decoded. The HARQ-ACK information mayinclude a HARQ-ACK codebook that includes one or more HARQ-ACK status(or HARQ-ACK bits).

For example, the correspondence between the HARQ-ACK information and thetransport block may mean that the HARQ-ACK information and the PDSCHused for transmission of the transport block correspond.

HARQ-ACK status may indicate ACK or NACK which correspond to one CBG(Code Block Group) included in the transport block.

The scheduling request may at least be used to request PUSCH (or UL-SCH)resources for new transmission. The scheduling request may be used toindicate either a positive SR or a negative SR. The fact that thescheduling request indicates a positive SR is also referred to as “apositive SR is sent”. The positive SR may indicate that the PUSCH (orUL-SCH) resource for initial transmission is requested by the terminaldevice 1. A positive SR may indicate that a higher-layer is to trigger ascheduling request. The positive SR may be sent when the higher-layerinstructs to send a scheduling request. The fact that the schedulingrequest bit indicates a negative SR is also referred to as “a negativeSR is sent”. A negative SR may indicate that the PUSCH (or UL-SCH)resource for initial transmission is not requested by the terminaldevice 1. A negative SR may indicate that the higher-layer does nottrigger a scheduling request. A negative SR may be sent if thehigher-layer is not instructed to send a scheduling request.

The channel state information may include at least part or all of achannel quality indicator (CQI), a precoder matrix indicator (PMI), anda rank indicator (RI). CQI is an indicator related to channel quality(e.g., propagation quality) or physical channel quality, and PMI is anindicator related to a precoder. RI is an indicator related totransmission rank (or the number of transmission layers).

Channel state information may be provided at least based on receivingone or more physical signals (e.g., one or more CSI-RSs) used at leastfor channel measurement. The channel state information may be selectedby the terminal device 1 at least based on receiving one or morephysical signals used for channel measurement. Channel measurements mayinclude interference measurements.

A PUCCH may correspond to a PUCCH format. A PUCCH may be a set ofresource elements used to convey a PUCCH format. A PUCCH may include aPUCCH format. A PUCCH format may include UCI.

A PUSCH may be used to transmit uplink data (a transport block) and/oruplink control information. A PUSCH may be used to transmit uplink data(a transport block) corresponding to a UL-SCH and/or uplink controlinformation. A PUSCH may be used to convey uplink data (a transportblock) and/or uplink control information. A PUSCH may be used to conveyuplink data (a transport block) corresponding to a UL-SCH and/or uplinkcontrol information. Uplink data (a transport block) may be arranged ina PUSCH. Uplink data (a transport block) corresponding to UL-SCH may bearranged in a PUSCH. Uplink control information may be arranged to aPUSCH. The terminal device 1 may transmit a PUSCH in which uplink data(a transport block) and/or uplink control information is arranged. Thebase station device 3 may receive a PUSCH in which uplink data (atransport block) and/or uplink control information is arranged.

A PRACH may be used to transmit a random-access preamble. The PRACH maybe used to convey a random-access preamble. The sequence x_(u,v)(n) ofthe PRACH is defined by x_(u,v)(n)=x_(u) (mod (n+C_(v), L_(RA))). Thex_(u) may be a ZC sequence (Zadoff-Chu sequence). The x_(u) may bedefined by x_(u)=exp (−jpui (i+1)/L_(RA)). The j is an imaginary unit.The p is the circle ratio. The C_(v) corresponds to cyclic shift of thePRACH. L_(RA) corresponds to the length of the PRACH. The L_(RA) may be839 or 139 or another value. The i is an integer in the range of 0 toL_(RA)−1. The u is a sequence index for the PRACH. The terminal device 1may transmit the PRACH. The base station device 3 may receive the PRACH.

For a given PRACH opportunity, 64 random-access preambles are defined.The random-access preamble is specified (determined, given) at leastbased on the cyclic shift C_(v) of the PRACH and the sequence index ufor the PRACH.

An uplink physical signal may correspond to a set of resource elements.The uplink physical signal may not carry information generated in thehigher-layer. The uplink physical signal may be a physical signal usedin the uplink component carrier. The terminal device 1 may transmit anuplink physical signal. The base station device 3 may receive the uplinkphysical signal. In the radio communication system according to oneaspect of the present embodiment, at least a part or all of UL DMRS(UpLink Demodulation Reference Signal), SRS (Sounding Reference Signal),UL PTRS (UpLink Phase Tracking Reference Signal) may be used.

UL DMRS is a generic name of a DMRS for a PUSCH and a DMRS for a PUCCH.

A set of antenna ports of a DMRS for a PUSCH (a DMRS associated with aPUSCH, a DMRS included in a PUSCH, a DMRS which corresponds to a PUSCH)may be given based on a set of antenna ports for the PUSCH. That is, theset of DMRS antenna ports for the PUSCH may be the same as the set ofantenna ports for the PUSCH.

Transmission of a PUSCH and transmission of a DMRS for the PUSCH may beindicated (or scheduled) by one DCI format. The PUSCH and the DMRS forthe PUSCH may be collectively referred to as a PUSCH. Transmission ofthe PUSCH may be transmission of the PUSCH and the DMRS for the PUSCH.

A PUSCH may be estimated from a DMRS for the PUSCH. That is, propagationpath of the PUSCH may be estimated from the DMRS for the PUSCH.

A set of antenna ports of a DMRS for a PUCCH (a DMRS associated with aPUCCH, a DMRS included in a PUCCH, a DMRS which corresponds to a PUCCH)may be identical to a set of antenna ports for the PUCCH.

Transmission of a PUCCH and transmission of a DMRS for the PUCCH may beindicated (or triggered) by one DCI format. The arrangement of the PUCCHin resource elements (resource element mapping) and/or the arrangementof the DMRS in resource elements for the PUCCH may be provided at leastby one PUCCH format. The PUCCH and the DMRS for the PUCCH may becollectively referred to as PUCCH. Transmission of the PUCCH may betransmission of the PUCCH and the DMRS for the PUCCH.

A PUCCH may be estimated from a DMRS for the PUCCH. That is, propagationpath of the PUCCH may be estimated from the DMRS for the PUCCH.

A downlink physical channel may correspond to a set of resource elementsthat carry information originating from the higher-layer and/or downlinkcontrol information. The downlink physical channel may be a physicalchannel used in the downlink component carrier. The base station device3 may transmit the downlink physical channel. The terminal device 1 mayreceive the downlink physical channel. In the wireless communicationsystem according to one aspect of the present embodiment, at least apart or all of PBCH (Physical Broadcast Channel), PDCCH (PhysicalDownlink Control Channel), and PDSCH (Physical Downlink Shared Channel)may be used.

The PBCH may be used to transmit a MIB (Master Information Block) and/orphysical layer control information. The physical layer controlinformation is a kind of downlink control information. The PBCH may besent to deliver the MIB and/or the physical layer control information.ABCH may be mapped (or corresponding) to the PBCH. The terminal device 1may receive the PBCH. The base station device 3 may transmit the PBCH.The physical layer control information is also referred to as a PBCHpayload and a PBCH payload related to timing. The MIB may include one ormore higher-layer parameters.

Physical layer control information includes 8 bits. The physical layercontrol information may include at least part or all of 0A to 0D. The 0Ais radio frame information. The 0B is half radio frame information (halfsystem frame information). The 0C is SS/PBCH block index information.The 0D is subcarrier offset information.

The radio frame information is used to indicate a radio frame in whichthe PBCH is transmitted (a radio frame including a slot in which thePBCH is transmitted). The radio frame information is represented by 4bits. The radio frame information may be represented by 4 bits of aradio frame indicator. The radio frame indicator may include 10 bits.For example, the radio frame indicator may at least be used to identifya radio frame from index 0 to index 1023.

The half radio frame information is used to indicate whether the PBCH istransmitted in first five subframes or in second five subframes amongradio frames in which the PBCH is transmitted. Here, the half radioframe may be configured to include five subframes. The half radio framemay be configured by five subframes of the first half of ten subframesincluded in the radio frame. The half radio frame may be configured byfive subframes in the second half of ten subframes included in the radioframe.

The SS/PBCH block index information is used to indicate an SS/PBCH blockindex. The SS/PBCH block index information may be represented by 3 bits.The SS/PBCH block index information may consist of 3 bits of an SS/PBCHblock index indicator. The SS/PBCH block index indicator may include 6bits. The SS/PBCH block index indicator may at least be used to identifyan SS/PBCH block from index 0 to index 63 (or from index 0 to index 3,from index 0 to index 7, from index 0 to index 9, from index 0 to index19, etc.).

The subcarrier offset information is used to indicate subcarrier offset.The subcarrier offset information may be used to indicate the differencebetween the first subcarrier in which the PBCH is arranged and the firstsubcarrier in which the control resource set with index 0 is arranged.

A PDCCH may be used to transmit downlink control information (DCI). APDCCH may be transmitted to deliver downlink control information.Downlink control information may be mapped to a PDCCH. The terminaldevice 1 may receive a PDCCH in which downlink control information isarranged. The base station device 3 may transmit the PDCCH in which thedownlink control information is arranged.

Downlink control information may correspond to a DCI format. Downlinkcontrol information may be included in a DCI format. Downlink controlinformation may be arranged in each field of a DCI format.

DCI format is a generic name for DCI format 0_0, DCI format 0_1, DCIformat 1_0, and DCI format 1_1. Uplink DCI format is a generic name ofthe DCI format 0_0 and the DCI format 0_1. Downlink DCI format is ageneric name of the DCI format 1_0 and the DC format 1_1.

The DCI format 0_0 is at least used for scheduling a PUSCH for a cell(or a PUSCH arranged on a cell). The DCI format 0_0 includes at least apart or all of fields 1A to 1E. The 1A is a DCI format identificationfield (Identifier field for DCI formats). The 1B is a frequency domainresource assignment field (FDRA field, FDRA information field). The 1Cis a time domain resource assignment field (TDRA field, TDRA informationfield). The 1D is a frequency-hopping flag field. The 1E is an MCS field(Modulation-and-Coding-Scheme field).

Frequency domain resource assignment field may be referred to as FDRAfield or FDRA information field.

Time domain resource assignment field may be referred to as TDRA fieldor TDRA information field.

The DCI format identification field may indicate whether the DCI formatincluding the DCI format identification field is an uplink DCI format ora downlink DCI format. The DCI format identification field included inthe DCI format 0_0 may indicate 0 (or may indicate that the DCI format0_0 is an uplink DCI format).

The frequency domain resource assignment field included in the DCIformat 0_0 may be at least used to indicate the assignment (allocation)of frequency resources for a PUSCH. The frequency domain resourceassignment field included in the DCI format 0_0 may be at least used toindicate the assignment (allocation) of frequency resources for a PUSCHscheduled by the DCI format 0_0.

The time domain resource assignment field included in the DCI format 00may be at least used to indicate the assignment of time resources for aPUSCH. The time domain resource assignment field included in the DCIformat 0_0 may be at least used to indicate the assignment of timeresources for a PUSCH scheduled by the DCI format 0_0.

The frequency-hopping flag field may be at least used to indicatewhether frequency-hopping is applied to a PUSCH. The frequency-hoppingflag field may be at least used to indicate whether frequency-hopping isapplied to a PUSCH scheduled by the DCI format 0_0.

The MCS field included in the DCI format 0_0 may be at least used toindicate a modulation scheme for a PUSCH and/or a part or all of atarget coding rate for the PUSCH. The MCS field included in the DCIformat 00 may be at least used to indicate a modulation scheme for aPUSCH scheduled by the DCI format 0_0 and/or a part or all of a targetcoding rate for the PUSCH. A size of a transport block (TBS: TransportBlock Size) of a PUSCH may be given based at least on a target codingrate and a part or all of a modulation scheme for the PUSCH. Themodulation scheme may include at least one of modulation order, targetcode rate and spectral efficiency.

The DCI format 0_0 may not include fields used for a CSI request. Thatis, CSI may not be requested by the DCI format 0_0.

The DCI format 00 may not include a carrier indicator field. An uplinkcomponent carrier on which a PUSCH scheduled by the DCI format 0_0 isarranged may be the same as an uplink component carrier on which a PDCCHincluding the DCI format 0_0 is arranged.

The DCI format 0_0 may not include a BWP field. An uplink BWP on which aPUSCH scheduled by the DCI format 0_0 is arranged may be the same as anuplink BWP on which a PDCCH including the DCI format 0_0 is arranged.

The DCI format 0_1/0_2 is at least used for scheduling of a PUSCH for acell (or arranged on a cell). The DCI format 0_1/0_2 includes at least apart or all of fields 2A to 2H. The 2A is a DCI format identificationfield. The 2B is a frequency domain resource assignment field. The 2C isa time domain resource assignment field. The 2D is a frequency-hoppingflag field. The 2E is an MCS field. The 2F is a CSI request field. The2G is a BWP field. The 2H is a carrier indicator field.

The DCI format identification field included in the DCI format 0_1/0_2may indicate 0 (or may indicate that the DCI format 0_1/0_2 is an uplinkDCI format).

The frequency domain resource assignment field included in the DCIformat 0_1/0_2 may be at least used to indicate the assignment offrequency resources for a PUSCH. The frequency domain resourceassignment field included in the DCI format 0_1/0_2 may be at least usedto indicate the assignment of frequency resources for a PUSCH scheduledby the DCI format.

The time domain resource assignment field included in the DCI format0_1/0_2 may be at least used to indicate the assignment of timeresources for a PUSCH. The time domain resource assignment fieldincluded in DCI format 0_1/0_2 may be at least used to indicate theassignment of time resources for a PUSCH scheduled by the DCI format0_1/0_2.

The frequency-hopping flag field may be at least used to indicatewhether frequency-hopping is applied to a PUSCH scheduled by the DCIformat 0_1/0_2.

The MCS field included in the DCI format 0_1/0_2 may be at least used toindicate a modulation scheme for a PUSCH and/or a part or all of atarget coding rate for the PUSCH. The MCS field included in the DCIformat 0_1/0_2 may be at least used to indicate a modulation scheme fora PUSCH scheduled by the DCI format and/or part or all of a targetcoding rate for the PUSCH.

When the DCI format 0_1 includes the BWP field, the BWP field may beused to indicate an uplink BWP on which a PUSCH scheduled by the DCIformat 0_1 is arranged. When the DCI format 0_1/0_2 does not include theBWP field, an uplink BWP on which a PUSCH is arranged may be the activeuplink BWP. When the number of uplink BWPs configured in the terminaldevice 1 in an uplink component carrier is two or more, the number ofbits for the BWP field included in the DCI format 0_1/0_2 used forscheduling a PUSCH arranged on the uplink component carrier may be oneor more. When the number of uplink BWPs configured in the terminaldevice 1 in a uplink component carrier is one, the number of bits forthe BWP field included in the DCI format 0_1/0_2 used for scheduling aPUSCH arranged on the uplink component carrier may be zero.

The CSI request field is at least used to indicate CSI reporting.

If the DCI format 0_1/0_2 includes the carrier indicator field, thecarrier indicator field may be used to indicate an uplink componentcarrier (or a serving cell) on which a PUSCH is arranged. When the DCIformat 0_1/0_2 does not include the carrier indicator field, a servingcell on which a PUSCH is arranged may be the same as the serving cell onwhich a PDCCH including the DCI format 0_1/0_2 used for scheduling ofthe PUSCH is arranged. When the number of uplink component carriers (orthe number of serving cells) configured in the terminal device 1 in aserving cell group is two or more (when uplink carrier aggregation isoperated in a serving cell group), or when cross-carrier scheduling isconfigured for the serving cell group, the number of bits for thecarrier indicator field included in the DCI format 0_1/0_2 used forscheduling a PUSCH arranged on the serving cell group may be one or more(e.g., 3). When the number of uplink component carriers (or the numberof serving cells) configured in the terminal device 1 in a serving cellgroup is one (or when uplink carrier aggregation is not operated in aserving cell group), or when the cross-carrier scheduling is notconfigured for the serving cell group, the number of bits for thecarrier indicator field included in the DCI format 0 I/O 2 used forscheduling of a PUSCH arranged on the serving cell group may be zero.

Also, the DCI format 0_1/0_2 may include one or more DCI fields of a SRSresource set indicator field, a SRS resource indicator field, a secondSRS resource indicator field, a precoding information and number oflayers field, a second precoding information field, an antenna portsfield, a DMRS sequence initialization field, a PTRS-DMRS associationfield, and/or a second PTRS-DMRS association field.

The number of bits for the SRS resource set indicator field may bedetermined as 0 or 2 bits based on one or more conditions. The number ofbits for the DCI field may be 2 bits if txConfig is configured to‘nonCodeBook’, and there are two SRS resource sets configured bysrs-ResourceSetToAddModListDCI-0-2 and associated with the usage ofvalue ‘nonCodeBook’, or if txConfig is configured to ‘codebook’, andthere are two SRS resource sets configured bysrs-ResourceSetToAddModListDCI-0-2 and associated with usage of value‘codebook’. Otherwise, the number of bits for the DCI field may be 0bit.

The precoding information and number of layers field may indicateprecoding information (i.e. TPMI value) and number of layers for thePUSCH transmission scheduled by the DCI format 0_1/0_2.

The number of bits for the precoding information and number of layersfield may be determined as any of 0, 1, 2, 3, 4, 5, 6 and more bitsbased on one or more conditions according to whether transform precoderis enabled or disabled, the number of antenna ports, the values of theRRC parameters txConfig, ul-FullPowerTransmission, maxRank, andcodebookSubset for the DCI format 0_1 or maxRankDCI-0-2 andcodebookSubsetDCI-0-2 for DCI format 0_2.

For example, the number of bits for the precoding information and numberof layers field may be 0 bits if the RRC parameter txConfig isconfigured to ‘nonCodebook’. The number of bits for the DCI field may be0 bits for 1 antenna port and if the RRC parameter txConfig isconfigured to ‘codebook’. The number of bits is 4, 5, or 6 bits for 4antenna ports, if the RRC parameter txConfig is configured to‘codebook’, the RRC parameter ul-FullPowerTransmission is notconfigured, or configured to ‘fullpowerMode2’ or configured to‘fullpower’, transform precoder is disabled, and according to the valuesof the RRC parameters maxRank, and codebookSubset for the DCI format 0_1or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2. Thenumber of bits for the DCI field may be 4 or 5 bits for 4 antenna ports,if txConfig is configured to ‘codebook’, ul-FullPowerTransmission isconfigured to ‘fullpowerMode1’, maxRank for the DCI format 0_1 ormaxRankDCI-0-2 for the DCI format 0_2 is configured to ‘2’, transformprecoder is disabled, and according to the values of the RRC parametercodebookSubset. The number of bits for the DCI field may be 4 or 6 bitsfor 4 antenna ports, if txConfig is configured to ‘codebook’,ul-FullPowerTransmission is configured to ‘fullpowerMode1’, maxRank forthe DCI format 0_1 or maxRankDCI-0-2 for the DCI format 0_2 isconfigured to ‘3’ or ‘4’, transform precoder is disabled, and accordingto the values of the RRC parameter codebookSubset for the DCI format 0_1or codebookSubsetDCI-0-2 for the DCI format 0_2. The number of bits forthe DCI field may be 2, 4, or 5 bits for 4 antenna ports, if txConfig isconfigured to ‘codebook’, ul-FullPowerTransmission is not configured orconfigured to ‘fullpowerMode2’ or configured to ‘fullpower’, andaccording to whether transform precoder is enabled or disabled, and thevalues of the RRC parameters maxRank, and codebookSubset for the DCIformat 0_1 or maxRankDCI-0-2, and codebookSubsetDCI-0-2 for the DCIformat 0_2. The number of bits for the DCI field may be 3 or 4 bits for4 antenna ports, if txConfig is configured to ‘codebook’,ul-FullPowerTransmission is configured to ‘fullpowerMode1’, maxRank forthe DCI format 0_1 or maxRankDCI-0-2 for the DCI format 0_2 isconfigured to ‘1’, and according to whether transform precoder isenabled or disabled, and the values of the RRC parameter codebookSubsetfor the DCI format 0_1 or codebookSubsetDCI-0-2 for the DCI format 0_2.The number of bits for the DCI field may be 2 or 4 bits for 2 antennaports, if txConfig is configured to ‘codebook’, ul-FullPowerTransmissionis not configured or configured to ‘fullpowerMode2’ or configured to‘fullpower’, transform precoder is disabled, and according to the valuesof the RRC parameters maxRank and codebookSubset for the DCI format 0_1or maxRankDCI-0-2, and codebookSubsetDCI-0-2 for the DCI format 0_2. Thenumber of bits for the DCI field may be 2 bits for 2 antenna ports, iftxConfig is configured to ‘codebook’, ul-FullPowerTransmission isconfigured to ‘fullpowerMode1’, transform precoder is disabled, maxRankfor the DCI format 0_1 or maxRankDCI-0-2 for the DCI format 0_2 isconfigured to ‘2’, and codebookSubset for the DCI format 0_1 orcodebookSubsetDCI-0-2 for the DCI format 0_2 is configured to‘nonCoherent’. The number of bits for the DCI field may be 1 or 3 bitsfor 2 antenna ports, if txConfig is configured to ‘codebook’,ul-FullPowerTransmission is not configured or configured to‘fullpowerMode2’ or configured to ‘fullpower’, and according to whethertransform precoder is enabled or disabled, and the values of the RRCparameters maxRank and codebookSubset for the DCI format 0_1 ormaxRankDCI-0-2 and codebookSubsetDCI-0-2 for the DCI format 0_2. Thenumber of bits for the DCI field may be 2 bits for 2 antenna ports, iftxConfig is configured to ‘codebook’, ul-FullPowerTransmission isconfigured to ‘fullpowerMode1’, maxRank for the DCI format 0_1 ormaxRankDCI-0-2 for the DCI format 0_2 is configured to ‘1’, andaccording to whether transform precoder is enabled or disabled, and thevalues of the RRC parameter codebookSubset for the DCI format 0_1 orcodebookSubsetDCI-0-2 for the DCI format 0_2.

Each of FIGS. 26, 27, and 28 is an example of a table used for theprecoding information and number of layers field in the DCI format0_1/0_2 determined based on the values of the RRC parameters txConfig,ul-FullPowerTransmission, maxRank, and/or codebookSubset, and/or numberof antenna ports, and/or the transform precoder enabled or disabled.

The number of bits used for the precoding information and number oflayers field in the DCI format 0_1/0_2 may be determined according tothe table.

For the RRC parameter txConfig configured to ‘codebook’, iful-FullPowerTransmission is configured to ‘fullpowerMode2’, each ofmaxRank for the DCI format 0_1 and/or maxRankDCI-0-2 for the DCI format02 is configured to be larger than 2, and at least one SRS resource with4 antenna ports is configured in the SRS resource set indicated by SRSresource set indicator field if present, otherwise in an SRS resourceset with usage set to ‘codebook’, and an SRS resource with 2 antennaports is indicated via SRI in the same SRS resource set, thencorresponding table may be used.

For the RRC parameter txConfig configured to ‘codebook’, if differentSRS resources with different number of antenna ports are configured, thebitwidth is determined according to the maximum number of ports in anSRS resource among the configured SRS resources in all SRS resourceset(s) with usage set to ‘codebook’. If the number of ports for aconfigured SRS resource in the set is less than the maximum number ofports in an SRS resource among the configured SRS resources, a number ofmost significant bits with value set to ‘0’ are inserted to the field.

The txConfig may be used for indicating whether the UE uses codebookbased or non-codebook based transmission. If the txConfig is absent, theUE transmits PUSCH on one antenna port.

The ul-FullPowerTransmission may be used for configuring the UE with ULfull power transmission mode.

The maxRank and the maxRankDCI-0-2 may be used for indicating subset ofPMIs addressed by TRIs from 1 to ULmaxRank. The field maxRank applies toDCI format 0_1 and the field maxRankDCI-0-2 applies to DCI format 0_2.

The codebookSubset and the codebookSubsetDCI-0-2 may be used forindicating Subset of PMIs addressed by TPMI, where PMIs are thosesupported by UEs with maximum coherence capabilities. The fieldcodebookSubset applies to DCI format 0_1 and the fieldcodebookSubsetDCI-0-2 applies to DCI format 0_2.

The second precoding information field may indicate precodinginformation (i.e. TPMI value) and number of layers for the PUSCH/SRStransmission scheduled by the DCI format 0_1/0_2.

The number of bits for the second precoding information field may bedetermined as any of 0, 1, 2, 3, 4, 5, 6 and more bits based on one ormore conditions according to whether transform precoder is enabled ordisabled, the number of antenna ports, the values of the RRC parameterstxConfig, ul-FullPowerTransmission, maxRank, and codebookSubset for theDCI format 0_1 or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCIformat 0_2.

For example, the number of bits for the second precoding informationfield may be 0 bits if SRS resource set indicator field is not present.The number of bits for the DCI field may be 0 bits if the RRC parametertxConfig is configured to ‘nonCodebook’. The number of bits for the DCIfield may be 0 bits for 1 antenna port and if the RRC parameter txConfigis configured to ‘codebook’. The number of bits for the DCI field may be3, 4, or 5 bits according to an associated table with the same number oflayers indicated by the precoding information and number of layers fieldfor 4 antenna ports, if SRS resource set indicator field is present,txConfig is configured to ‘codebook’, ul-FullPowerTransmission is notconfigured or configured to ‘fullpowerMode2’ or configured to‘fullpower’, transform precoder is disabled, and according to the valuesof the RRC parameters maxRank, and codebookSubset for the DCI format 0_1or maxRankDCI-0-2 and codebookSubset for the DCI format 0_2. The numberof bits for the DCI field may be 4 bits according to an associated tablewith the same number of layers indicated by the precoding informationand number of layers field for 4 antenna ports, if SRS resource setindicator field is present, txConfig is configured to ‘codebook’,ul-FullPowerTransmission is configured to ‘fullpowerMode1’, maxRank forthe DCI format 0_1 or maxRankDCI-0-2 for the DCI format 0_2 isconfigured to ‘2’, transform precoder is disabled, and according to thevalues of the RRC parameter codebookSubset for the DCI format 0_1 orcodebookSubsetDCI-0-2 for the DCI format 0_2. The number of bits for theDCI field may be 4 bits according to an associated table with the samenumber of layers indicated by the precoding information and number oflayers field for 4 antenna ports, if SRS resource set indicator field ispresent, txConfig is configured to ‘codebook’, ul-FullPowerTransmissionis configured to ‘fullpowerMode1’, maxRank is configured to ‘3’ or ‘4’,transform precoder is disabled, and according to the values of the RRCparameter codebookSubset for the DCI format 0_1 orcodebookSubsetDCI-0-2. The number of bits for the DCI field may be 2, 4,or 5 bits according to an associated table with the same number oflayers indicated by the precoding information and number of layers fieldfor 4 antenna ports, if SRS resource set indicator field is present,txConfig is configured to ‘codebook’, ul-FullPowerTransmission is notconfigured or configured to ‘fullpowerMode2’ or configured to‘fullpower’, and according to whether transform precoder is enabled ordisabled, and the values of the RRC parameters maxRank, andcodebookSubset for the DCI format 0_1 or maxRankDCI-0-2, andcodebookSubsetDCI-0-2 for the DCI format 0_2. The number of bits for theDCI field may be 3 or 4 bits according to an associated table with thesame number of layers indicated by the precoding information and numberof layers field for 4 antenna ports, if SRS resource set indicator fieldis present, txConfig is configured to ‘codebook’,ul-FullPowerTransmission is configured to ‘fullpowerMode1’, maxRank forDCI format 0_1 or maxRankDCI-0-2 is configured to ‘1’, and according towhether transform precoder is enabled or disabled, and the values of theRRC parameter codebookSubset for DCI format 0_1 or codebookSubsetDCI-0-2for DCI format 0_2. The number of bits for the DCI field may be 1 or 3bits according to an associated table with the same number of layersindicated by the precoding information and number of layers field for 2antenna ports, if SRS resource set indicator field is present, txConfigis configured to ‘codebook’, ul-FullPowerTransmission is not configuredor configured to ‘fullpowerMode2’ or configured to ‘fullpower’,transform precoder is disabled, and according to the values of RRCparameters maxRank and codebookSubset for the DCI format 0_1 ormaxRankDCI-0-2 and codebookSubsetDCI-0-2 for the DCI format 0_2. Thenumber of bits for the DCI field may be 2 bits according to anassociated table with the same number of layers indicated by theprecoding information and number of layers field for 2 antenna ports, ifSRS resource set indicator field is present, txConfig is configured to‘codebook’, ul-FullPowerTransmission is configured to ‘fullpowerMode1’,transform precoder is disabled, maxRank for the DCI format 0_1 ormaxRankDCI-0-2 for the DCI format 0_2 is configured to ‘2’, andcodebookSubset for the DCI format 0_1 or codebookkSubsetDCI-0-2 isconfigured to ‘nonCoherent’. The number of bits for the DCI field may be1 or 3 bits according to an associated table with the same number oflayers indicated by the precoding information and number of layers fieldfor 2 antenna ports, if SRS resource set indicator field is present,txConfig is configured to ‘codebook’, ul-FullPowerTransmission is notconfigured or configured to ‘fullpowerMode2’ or configured to‘fullpower’, and according to whether transform precoder is enabled ordisabled, and the values of the RRC parameters maxRank andcodebookSubset for the DCI format 0_1 or maxRankDCI-0-2 andcodebookSubsetDCI-0-2 for the DCI format 0_2. The number of bits for theDCI field may be 2 bits according to an associated table with the samenumber of layers indicated by the precoding information and number oflayers field for 2 antenna ports, if SRS resource set indicator field ispresent, txConfig is configured to ‘codebook’, ul-FullPowerTransmissionis configured to ‘fullpowerMode1’, maxRank for the DCI format 0_1 ormaxRankDCI-0-2 for the DCI format 0_2 is configured to ‘ ’, andaccording to whether transform precoder is enabled or disabled, and thevalues of the RRC parameter codebookSubset for the DCI format 0_1 orcodebookSubsetDCI-0-2 for the DCI format 0_2.

Each of FIG. 29 and FIGS. 30A-30B is example(s) of a table used for thesecond precoding information field in the DCI format 0_1/0_2 determinedbased on the values of the RRC parameters txConfig,ul-FullPowerTransmission, maxRank, maxRankDCI-0-2 and/or codebookSubset,and/or number of antenna ports, and/or whether the transform precoder isenabled or disabled, number of layers indicated by the precodinginformation and number of layers field and whether the SRS resource setindicator field is present or not.

For the RRC parameter txConfig configured to ‘codebook’, iful-FullPowerTransmission is configured to ‘fullpowerMode2’, maxRank forthe DCI format 0_1 or maxRankDCI-0-2 for the DCI format 0_2 isconfigured to be larger than 2, and at least one SRS resource with 4antenna ports is configured in the SRS resource set indicated by SRSresource set indicator field, and an SRS resource with 2 antenna portsis indicated via Second SRS resource indicator field in the same SRSresource set, then an associated table is used.

For the RRC parameter txConfig configured to ‘codebook’, if differentSRS resources with different number of antenna ports are configured, thebitwidth is determined according to the maximum number of ports in anSRS resource among the configured SRS resources in the second SRSresource set with usage set to ‘codebook’ as defined in an associatedtable. If the number of ports for a configured SRS resource in the setis less than the maximum number of ports in an SRS resource among theconfigured SRS resources, a number of most significant bits with valueset to ‘0’ are inserted to the field.

The antenna ports field may indicate number of DMRS CDM group(s) withoutdata and DMRS port(s) and/or number of front load symbols.

The number of bits for the antenna ports field may be determined as anyof 2, 3, 4, 5 and more bits based on one or more conditions according towhether transform precoder is enabled or disabled, the value of rank,the values of the RRC parameters dmrs-Type, maxLength, txConfig,dmrs-UplinkTransformPrecoding and tp-pi2BPSK.

For example, the number of bits for the antenna ports field may be 2bits as defined by an associated table, if transform precoder isenabled, dmrs-Type is configured to ‘1’, and maxLength is configured to‘1’, except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are bothconfigured and 7/2 BPSK modulation is used. The number of bits for theDCI field may be 2 bits as defined by an associated table, if transformprecoder is enabled and dmrs-UplinkTransformPrecoding and tp-pi2BPSK areboth configured, π/2 BPSK modulation is used, dmrs-Type is configured to‘1’, and maxLength is configured to ‘1’, where n_(SCID) is thescrambling identity for antenna ports defined in the sequence generationmethod for DMRS for PUSCH when the transform precoding is enabled. Thenumber of bits for the DCI field may be 4 bits as defined by anassociated table, if transform precoder is enabled, dmrs-Type isconfigured to ‘1’, and maxLength is configured to ‘2’, except thatdmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2BPSK modulation is used. The number of bits for the DCI field may be 4bits as defined by an associated table, if transform precoder is enabledand dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured,n/2 BPSK modulation is used, dmrs-Type is configured to ‘1’, andmaxLength is configured to ‘2’, where n_(SCID) is the scramblingidentity for antenna ports defined in the sequence generation method forDMRS for PUSCH when the transform precoding is enabled. The number ofbits for the DCI field may be 3 bits as defined by associated tables, iftransform precoder is disabled, dmrs-Type is configured to 1, andmaxLength is configured to 1, and the value of rank is determinedaccording to the SRS resource indicator field if the RRC parametertxConfig is configured to ‘nonCodebook’ and according to the precodinginformation and number of layers field if the RRC parameter txConfig isconfigured to ‘codebook’. The number of bits for the DCI field may be 4bits as defined by associated tables, if transform precoder is disabled,dmrs-Type is configured to ‘1’, and maxLength is configured to ‘2’, andthe value of rank is determined according to the SRS resource indicatorfield if the higher layer parameter txConfig is configured to‘nonCodebook’ and according to the precoding information and number oflayers field if the RRC parameter txConfig is configured to ‘codebook’.The number of bits for the DCI field may be 4 bits as defined byassociated tables, if transform precoder is disabled, dmrs-Type isconfigured to ‘2’, and maxLength is configured to ‘1’, and the value ofrank is determined according to the SRS resource indicator field if theRRC parameter txConfig is configured to ‘nonCodebook’ and according tothe precoding information and number of layers field if the RRCparameter txConfig is configured to ‘codebook’. The number of bits forthe DCI field may be 5 bits as defined by associated tables, iftransform precoder is disabled, dmrs-Type is configured to ‘2’, andmaxLength is configured to ‘2’, and the value of rank is determinedaccording to the SRS resource indicator field if the RRC parametertxConfig is configured to ‘nonCodebook’ and according to the precodinginformation and number of layers field if the higher layer parametertxConfig is configured to ‘codebook’. And the number of CDM groupswithout data of values 1, 2, and 3 in associated tables refers to CDMgroups (0), {0,1}, and {0,1,2} respectively.

Each of FIGS. 31 and 32 is example(s) of a table used for the antennaports field in the DCI format 0_1/0_2 determined based on the values ofthe RRC parameters txConfig, maxLength, and/or dmrs-Type, whether or notdmrs-UplinkTransformPrecoding and/or tp-pi2BPSK are configured, and/orwhether the transform precoder is enabled or disabled, number of layersindicated by the precoding information and number of layers field andwhether the SRS resource set indicator field is present or not.

The dmrs-Type may be used for selection of the DMRS type to be used forUL. If the dmrs-Type is absent, the UE uses DMRS type 1.

The maxLength may be used for indicating the maximum number of OFDMsymbols for UL front loaded DMRS. len1 corresponds to value 1. len2corresponds to value 2. If the maxLength is absent, the UE applies valuelen1. If set to len2, the UE determines the actual number of DM-RSsymbols by the associated DCI.

The dmrs-UplinkTransformPrecoding may be used for indicating whether lowPAPR DMRS is used for PUSCH with pi/2 BPSK modulation. The network mayconfigure this field only if tp-pi2BPSK is configured in PUSCH-Config.

The tp-pi2BPSK may be used for indicating whether the UE enablespi/2-BPSK modulation with transform precoding if the field is presentand disables it otherwise.

The PTRS-DMRS association field may indicate DMRS port associated withUL PTRS port 0 and/or 1 or actual UL PTRS port.

The number of bits for the PTRS-DMRS association field may be determinedbased on one or more conditions according to whether PTRS-UplinkConfigis configured or not, maxNrofPorts, values of RRC parameters maxRank forthe DCI format 0_1, maxRankDCI-0-2 for the DCI format 0_2, values of theSRS resource indicator field and/or the precoding information and numberof layers field.

For example, the number of bits for the PTRS-DMRS association field maybe 0 bit if PTRS-UplinkConfig is not configured in eitherdmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB andtransform precoder is disabled, or if transform precoder is enabled, orif maxRank is configured to ‘1’. The number of bits for the DCI fieldmay be 2 bits otherwise, where associated tables are used to indicatethe association between PTRS port(s) and DMRS port(s) when one PT-RSport and two PT-RS ports are configured by maxNrofPorts inPTRS-UplinkConfig respectively, and the DMRS ports are indicated by theAntenna ports field. When the SRS resource set indicator field ispresent and maxRank>2, this field indicates the association between PTRSport(s) and DMRS port(s) corresponding to the SRS resource indicatorfield and/or the precoding information and number of layers fieldaccording to associated tables. When the SRS resource set indicatorfield is present and maxRank is configured to ‘2’, the MSB of this fieldindicates the association between PTRS port(s) and DMRS port(s)corresponding to the SRS resource indicator field and/or the precodinginformation and number of layers field, and the LSB of this fieldindicates the association between PTRS port(s) and DMRS port(s)corresponding to the second SRS resource indicator field and/or thesecond precoding information field, according to an associated table.

If the “bandwidth part indicator” field indicates a bandwidth part otherthan the active bandwidth part and the “PTRS-DMRS association” field ispresent for the indicated bandwidth part but not present for the activebandwidth part, the UE assumes the “PTRS-DMRS association” field is notpresent for the indicated bandwidth part.

The second PTRS-DMRS association field may indicate DMRS port associatedwith UL PTRS port 0 and/or 1.

The number of bits for the second PTRS-DMRS association field may be 2bits if the PTRS-DMRS association field and the SRS resource setindicator field are present and maxRank>2. The number of bits for theDCI field may be 0 bit otherwise. associated tables are used to indicatethe association between PTRS port(s) and DMRS port(s) corresponding tothe second SRS resource indicator field and/or the second precodinginformation field when one PT-RS port and two PT-RS ports are configuredby maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS portsare indicated by the Antenna ports field.

The DMRS sequence initialization field may indicate the value ofn_(SCID).

The number of bits for the DMRS sequence initialization field may bedetermined based on whether transform precoder is enabled or disabled.For example, the number of bits for the DCI field may be 0 bit iftransform precoder is enabled. The number of bits for the DCI field maybe 1 bit if transform precoder is disabled.

The DCI format 1_0 is at least used for scheduling of a PDSCH for a cell(arranged on a cell). The DCI format 1_0 includes at least a part or allof fields 3A to 3F. The 3A is a DCI format identification field. The 3Bis a frequency domain resource assignment field. The 3C is a time domainresource assignment field. The 3D is an MCS field. The 3E is aPDSCH-to-HARQ-feedback indicator field. The 3F is a PUCCH resourceindicator field.

The DCI format identification field included in the DCI format 10 mayindicate 1 (or may indicate that the DCI format 1_0 is a downlink DCIformat).

The frequency domain resource assignment field included in the DCIformat 1_0 may be at least used to indicate the assignment of frequencyresources for a PDSCH. The frequency domain resource assignment fieldincluded in the DCI format 1_0 may be at least used to indicate theassignment of frequency resources for a PDSCH scheduled by the DC format1_0.

The time domain resource assignment field included in the DCI format 10may be at least used to indicate the assignment of time resources for aPDSCH. The time domain resource assignment field included in the DCIformat 1_0 may be at least used to indicate the assignment of timeresources for a PDSCH scheduled by the DCI format 1_0.

The MCS field included in the DCI format 1_0 may be at least used toindicate a modulation scheme for a PDSCH and/or a part or all of atarget coding rate for the PDSCH. The MCS field included in the DCIformat 10 may be at least used to indicate a modulation scheme for aPDSCH scheduled by the DCI format 1_0 and/or a part or all of a targetcoding rate for the PDSCH. A size of a transport block (TBS: TransportBlock Size) of a PDSCH may be given based at least on a target codingrate and a part or all of a modulation scheme for the PDSCH.

The PDSCH-to-HARQ-feedback timing indicator field may be at least usedto indicate the offset (K1) from a slot in which the last OFDM symbol ofa PDSCH scheduled by the DCI format 1_0 is included to another slot inwhich the first OFDM symbol of a PUCCH triggered by the DCI format 1_0is included.

The PUCCH resource indicator field may be a field indicating an index ofany one or more PUCCH resources included in the PUCCH resource set for aPUCCH transmission. The PUCCH resource set may include one or more PUCCHresources. The PUCCH resource indicator field may trigger PUCCHtransmission with a PUCCH resource indicated at least based on the PUCCHresource indicator field.

The DCI format 1_0 may not include the carrier indicator field. Adownlink component carrier on which a PDSCH scheduled by the DCI format1_0 is arranged may be the same as a downlink component carrier on whicha PDCCH including the DCI format 1_0 is arranged.

The DCI format 1_0 may not include the BWP field. A downlink BWP onwhich a PDSCH scheduled by a DCI format 1_0 is arranged may be the sameas a downlink BWP on which a PDCCH including the DCI format 1_0 isarranged.

The DCI format 1_1 is at least used for scheduling of a PDSCH for a cell(or arranged on a cell). The DCI format 1_1 includes at least a part orall of fields 4A to 4H. The 4A is a DCI format identification field. The4B is a frequency domain resource assignment field. The 4C is a timedomain resource assignment field. The 4D is an MCS field. The 4E is aPDSCH-to-HARQ-feedback indicator field. The 4F is a PUCCH resourceindicator field. The 4G is a BWP field. The 4H is a carrier indicatorfield.

The DCI format identification field included in the DCI format 1_1 mayindicate 1 (or may indicate that the DCI format 1_1 is a downlink DCIformat).

The frequency domain resource assignment field included in the DCIformat 1_1 may be at least used to indicate the assignment of frequencyresources for a PDSCH. The frequency domain resource assignment fieldincluded in the DCI format 1_0 may be at least used to indicate theassignment of frequency resources for a PDSCH scheduled by the DCIformat 1_1.

The time domain resource assignment field included in the DCI format 1_1may be at least used to indicate the assignment of time resources for aPDSCH. The time domain resource assignment field included in the DCIformat 11 may be at least used to indicate the assignment of timeresources for a PDSCH scheduled by the DCI format 1_1.

The MCS field included in the DCI format 11 may be at least used toindicate a modulation scheme for a PDSCH and/or a part or all of atarget coding rate for the PDSCH. The MCS field included in the DCIformat 1_1 may be at least used to indicate a modulation scheme for aPDSCH scheduled by the DCI format 1_1 and/or a part or all of a targetcoding rate for the PDSCH.

When the DCI format 1_1 includes a PDSCH-to-HARQ-feedback timingindicator field, the PDSCH-to-HARQ-feedback timing indicator fieldindicates an offset (K1) from a slot including the last OFDM symbol of aPDSCH scheduled by the DCI format 1_1 to another slot including thefirst OFDM symbol of a PUCCH triggered by the DCI format 1_1. When theDCI format 1_1 does not include the PDSCH-to-HARQ-feedback timingindicator field, an offset from a slot in which the last OFDM symbol ofa PDSCH scheduled by the DCI format 1_1 is included to another slot inwhich the first OFDM symbol of a PUCCH triggered by the DCI format 1_1is identified by a higher-layer parameter.

When the DCI format 1_1 includes the BWP field, the BWP field may beused to indicate a downlink BWP on which a PDSCH scheduled by the DCIformat 1_1 is arranged. When the DCI format 1_1 does not include the BWPfield, a downlink BWP on which a PDSCH is arranged may be the activedownlink BWP. When the number of downlink BWPs configured in theterminal device 1 in a downlink component carrier is two or more, thenumber of bits for the BWP field included in the DCI format 1_1 used forscheduling a PDSCH arranged on the downlink component carrier may be oneor more. When the number of downlink BWPs configured in the terminaldevice 1 in a downlink component carrier is one, the number of bits forthe BWP field included in the DCI format 1_1 used for scheduling a PDSCHarranged on the downlink component carrier may be zero.

If the DCI format 1_1 includes the carrier indicator field, the carrierindicator field may be used to indicate a downlink component carrier (ora serving cell) on which a PDSCH is arranged. When the DCI format 1_1does not include the carrier indicator field, a downlink componentcarrier (or a serving cell) on which a PDSCH is arranged may be the sameas a downlink component carrier (or a serving cell) on which a PDCCHincluding the DCI format 1_1 used for scheduling of the PDSCH isarranged. When the number of downlink component carriers (or the numberof serving cells) configured in the terminal device 1 in a serving cellgroup is two or more (when downlink carrier aggregation is operated in aserving cell group), or when cross-carrier scheduling is configured forthe serving cell group, the number of bits for the carrier indicatorfield included in the DCI format 1_1 used for scheduling a PDSCHarranged on the serving cell group may be one or more (e.g., 3). Whenthe number of downlink component carriers (or the number of servingcells) configured in the terminal device 1 in a serving cell group isone (or when downlink carrier aggregation is not operated in a servingcell group), or when the cross-carrier scheduling is not configured forthe serving cell group, the number of bits for the carrier indicatorfield included in the DCI format 1_1 used for scheduling of a PDSCHarranged on the serving cell group may be zero.

A PDSCH may be used to transmit one or more transport blocks. A PDSCHmay be used to transmit one or more transport blocks which correspondsto a DL-SCH. A PDSCH may be used to convey one or more transport blocks.A PDSCH may be used to convey one or more transport blocks whichcorresponds to a DL-SCH. One or more transport blocks may be arranged ina PDSCH. One or more transport blocks which corresponds to a DL-SCH maybe arranged in a PDSCH. The base station device 3 may transmit a PDSCH.The terminal device 1 may receive the PDSCH.

Downlink physical signals may correspond to a set of resource elements.The downlink physical signals may not carry the information generated inthe higher-layer. The downlink physical signals may be physical signalsused in the downlink component carrier. A downlink physical signal maybe transmitted by the base station device 3. The downlink physicalsignal may be transmitted by the terminal device 1. In the wirelesscommunication system according to one aspect of the present embodiment,at least a part or all of an SS (Synchronization signal), DL DMRS(DownLink DeModulation Reference Signal), CSI-RS (Channel StateInformation-Reference Signal), and DL PTRS (DownLink Phase TrackingReference Signal) may be used.

The synchronization signal may be used at least for the terminal device1 to synchronize in the frequency domain and/or time domain fordownlink. The synchronization signal is a generic name of PSS (PrimarySynchronization Signal) and SSS (Secondary Synchronization Signal).

FIG. 7 is a diagram showing a configuration example of an SS/PBCH blockaccording to an aspect of the present embodiment. In FIG. 7 , thehorizontal axis indicates time domain (OFDM symbol index l_(sym)), andthe vertical axis indicates frequency domain. The shaded blocks indicatea set of resource elements for a PSS. The blocks of grid lines indicatea set of resource elements for an SSS. Also, the blocks in thehorizontal line indicate a set of resource elements for a PBCH and a setof resource elements for a DMRS for the PBCH (DMRS related to the PBCH,DMRS included in the PBCH, DMRS which corresponds to the PBCH).

As shown in FIG. 7 , the SS/PBCH block includes a PSS, an SSS, and aPBCH. The SS/PBCH block includes 4 consecutive OFDM symbols. The SS/PBCHblock includes 240 subcarriers. The PSS is allocated to the 57th to183rd subcarriers in the first OFDM symbol. The SSS is allocated to the57th to 183rd subcarriers in the third OFDM symbol. The first to 56thsubcarriers of the first OFDM symbol may be set to zero. The 184th to240th subcarriers of the first OFDM symbol may be set to zero. The 49thto 56th subcarriers of the third OFDM symbol may be set to zero. The184th to 192nd subcarriers of the third OFDM symbol may be set to zero.In the first to 240th subcarriers of the second OFDM symbol, the PBCH isallocated to subcarriers in which the DMRS for the PBCH is notallocated. In the first to 48th subcarriers of the third OFDM symbol,the PBCH is allocated to subcarriers in which the DMRS for the PBCH isnot allocated. In the 193rd to 240th subcarriers of the third OFDMsymbol, the PBCH is allocated to subcarriers in which the DMRS for thePBCH is not allocated. In the first to 240th subcarriers of the 4th OFDMsymbol, the PBCH is allocated to subcarriers in which the DMRS for thePBCH is not allocated.

The antenna ports of a PSS, an SSS, a PBCH, and a DMRS for the PBCH inan SS/PBCH block may be identical.

A PBCH may be estimated from a DMRS for the PBCH. For the DM-RS for thePBCH, the channel over which a symbol for the PBCH on an antenna port isconveyed can be inferred from the channel over which another symbol forthe DM-RS on the antenna port is conveyed only if the two symbols arewithin a SS/PBCH block transmitted within the same slot, and with thesame SS/PBCH block index.

DL DMRS is a generic name of DMRS for a PBCH, DMRS for a PDSCH, and DMRSfor a PDCCH.

A set of antenna ports for a DMRS for a PDSCH (a DMRS associated with aPDSCH, a DMRS included in a PDSCH, a DMRS which corresponds to a PDSCH)may be given based on the set of antenna ports for the PDSCH. The set ofantenna ports for the DMRS for the PDSCH may be the same as the set ofantenna ports for the PDSCH.

Transmission of a PDSCH and transmission of a DMRS for the PDSCH may beindicated (or scheduled) by one DCI format. The PDSCH and the DMRS forthe PDSCH may be collectively referred to as PDSCH. Transmitting a PDSCHmay be transmitting a PDSCH and a DMRS for the PDSCH.

A PDSCH may be estimated from a DMRS for the PDSCH. For a DM-RSassociated with a PDSCH, the channel over which a symbol for the PDSCHon one antenna port is conveyed can be inferred from the channel overwhich another symbol for the DM-RS on the antenna port is conveyed onlyif the two symbols are within the same resource as the scheduled PDSCH,in the same slot, and in the same PRG (Precoding Resource Group).

Antenna ports for a DMRS for a PDCCH (a DMRS associated with a PDCCH, aDMRS included in a PDCCH, a DMRS which corresponds to a PDCCH) may bethe same as an antenna port for the PDCCH.

A PDCCH may be estimated from a DMRS for the PDCCH. For a DM-RSassociated with a PDCCH, the channel over which a symbol for the PDCCHon one antenna port is conveyed can be inferred from the channel overwhich another symbol for the DM-RS on the same antenna port is conveyedonly if the two symbols are within resources for which the UE may assumethe same precoding being used (i.e. within resources in a REG bundle).

A BCH (Broadcast CHannel), a UL-SCH (Uplink-Shared CHannel) and a DL-SCH(Downlink-Shared CHannel) are transport channels. A channel used in theMAC layer is called a transport channel. A unit of transport channelused in the MAC layer is also called transport block (TB) or MAC PDU(Protocol Data Unit). In the MAC layer, control of HARQ (HybridAutomatic Repeat request) is performed for each transport block. Thetransport block is a unit of data delivered by the MAC layer to thephysical layer. In the physical layer, transport blocks are mapped tocodewords and modulation processing is performed for each codeword.

One UL-SCH and one DL-SCH may be provided for each serving cell. BCH maybe given to PCell. BCH may not be given to PSCell and SCell.

A BCCH (Broadcast Control CHannel), a CCCH (Common Control CHannel), anda DCCH (Dedicated Control CHannel) are logical channels. The BCCH is achannel of the RRC layer used to deliver MIB or system information. TheCCCH may be used to transmit a common RRC message in a plurality ofterminal devices 1. The CCCH may be used for the terminal device 1 whichis not connected by RRC. The DCCH may be used at least to transmit adedicated RRC message to the terminal device 1. The DCCH may be used forthe terminal device 1 that is in RRC-connected mode.

The RRC message includes one or more RRC parameters (informationelements, higher layer parameters). For example, the RRC message mayinclude a MIB. For example, the RRC message may include systeminformation (SIB: System Information Block, MIB). SIB is a generic namefor various type of SIBs (e.g., SIB1, SIB2). For example, the RRCmessage may include a message which corresponds to a CCCH. For example,the RRC message may include a message which corresponds to a DCCH. RRCmessage is a general term for common RRC message and dedicated RRCmessage.

The BCCH in the logical channel may be mapped to the BCH or the DL-SCHin the transport channel. The CCCH in the logical channel may be mappedto the DL-SCH or the UL-SCH in the transport channel. The DCCH in thelogical channel may be mapped to the DL-SCH or the UL-SCH in thetransport channel.

The UL-SCH in the transport channel may be mapped to a PUSCH in thephysical channel. The DL-SCH in the transport channel may be mapped to aPDSCH in the physical channel. The BCH in the transport channel may bemapped to a PBCH in the physical channel.

A higher-layer parameter is a parameter included in an RRC message or aMAC CE (Medium Access Control Control Element). The higher-layerparameter is a generic name of information included in a MIB, systeminformation, a message which corresponds to CCCH, a message whichcorresponds to DCCH, and a MAC CE. A higher-layer parameter may bereferred to as an RRC parameter or an RRC configuration if thehigher-layer parameter is the parameter included in the RRC message.

A higher-layer parameter may be a cell-specific parameter or aUE-specific parameter. A cell-specific parameter is a parameterincluding a common configuration in a cell. A UE-specific parameter is aparameter including a configuration that may be configured differentlyfor each UE.

The base station device may indicate change of cell-specific parametersby reconfiguration with random-access. The UE may change cell-specificparameters before triggering random-access. The base station device mayindicate change of UE-specific parameters by reconfiguration with orwithout random-access. The UE may change UE-specific parameters beforeor after random-access.

The procedure performed by the terminal device 1 includes at least apart or all of the following 5A to 5C. The 5A is cell search. The 5B israndom-access. The 5C is data communication.

The cell search is a procedure used by the terminal device 1 tosynchronize with a cell in the time domain and/or the frequency domainand to detect a physical cell identity. The terminal device 1 may detectthe physical cell ID by performing synchronization of time domain and/orfrequency domain with a cell by the cell search.

A sequence of a PSS is given based at least on a physical cell ID. Asequence of an SSS is given based at least on the physical cell ID.

An SS/PBCH block candidate indicates a resource for which transmissionof the SS/PBCH block may exist. An SS/PBCH block may be transmitted at aresource indicated as the SS/PBCH block candidate. The base stationdevice 3 may transmit an SS/PBCH block at an SS/PBCH block candidate.The terminal device 1 may receive (detect) the SS/PBCH block at theSS/PBCH block candidate.

A set of SS/PBCH block candidates in a half radio frame is also referredto as an SS-burst-set. The SS-burst-set is also referred to as atransmission window, a SS transmission window, or a DRS transmissionwindow (Discovery Reference Signal transmission window). TheSS-burst-set is a generic name that includes at least a firstSS-burst-set and a second SS-burst-set.

The base station device 3 transmits SS/PBCH blocks of one or moreindexes at a predetermined cycle. The terminal device 1 may detect anSS/PBCH block of at least one of the SS/PBCH blocks of the one or moreindexes. The terminal device 1 may attempt to decode the PBCH includedin the SS/PBCH block.

The random-access is a procedure including at least a part or all ofmessage 1, message 2, message 3, and message 4.

The message 1 is a procedure in which the terminal device 1 transmits aPRACH. The terminal device 1 transmits the PRACH in one PRACH occasionselected from among one or more PRACH occasions based on at least theindex of the SS/PBCH block candidate detected based on the cell search.

The message 2 is a procedure in which the terminal device 1 attempts todetect a DCI format 1_0 with CRC (Cyclic Redundancy Check) scrambled byan RA-RNTI (Random Access-Radio Network Temporary Identifier). Theterminal device 1 may attempt to detect the DCI format 1_0 in asearch-space-set.

The message 3 (Msg 3) is a procedure for transmitting a PUSCH scheduledby a random-access response grant included in the DCI format 1_0detected in the message 2 procedure. The random-access response grant isindicated by the MAC CE included in the PDSCH scheduled by the DCIformat 1_0.

The PUSCH scheduled based on the random-access response grant is eithera message 3 PUSCH or a PUSCH. The message 3 PUSCH contains a contentionresolution identifier MAC CE. The contention resolution ID MAC CEincludes a contention resolution ID.

Retransmission of the message 3 PUSCH is scheduled by DCI format 0_0with CRC scrambled by a TC-RNTI (Temporary Cell-Radio Network TemporaryIdentifier).

The message 4 is a procedure that attempts to detect a DCI format 1_0with CRC scrambled by either a C-RNTI (Cell-Radio Network TemporaryIdentifier) or a TC-RNTI. The terminal device 1 receives a PDSCHscheduled based on the DCI format 1_0. The PDSCH may include a collisionresolution ID.

Data communication is a generic term for downlink communication anduplink communication.

In data communication, the terminal device 1 attempts to detect a PDCCH(attempts to monitor a PDCCH, monitors a PDCCH). in a resourceidentified at least based on one or all of a control resource set and asearch-space-set. It's also called as “the terminal device 1 attempts todetect a PDCCH in a control resource set”, “the terminal device 1attempts to detect a PDCCH in a search-space-set”, “the terminal device1 attempts to detect a PDCCH candidate in a control resource set”, “theterminal device 1 attempts to detect a PDCCH candidate in asearch-space-set”, “the terminal device 1 attempts to detect a DCIformat in a control resource set”, or “the terminal device 1 attempts todetect a DCI format in a search-space-set”. Monitoring a PDCCH may beequivalent as monitoring a DCI format in the PDCCH.

The control resource set is a set of resources configured by the numberof resource blocks and a predetermined number of OFDM symbols in a slot.

The set of resources for the control resource set may be indicated byhigher-layer parameters. The number of OFDM symbols included in thecontrol resource set may be indicated by higher-layer parameters.

A PDCCH may be also called as a PDCCH candidate.

A search-space-set is defined as a set of PDCCH candidates. Asearch-space-set may be a Common Search Space (CSS) set or a UE-specificSearch Space (USS) set.

The CSS set is a generic name of a type-0 PDCCH common search-space-set,a type-0a PDCCH common search-space-set, a type-1 PDCCH commonsearch-space-set, a type-2 PDCCH common search-space-set, and a type-3PDCCH common search-space-set. The USS set may be also called asUE-specific PDCCH search-space-set.

The type-0 PDCCH common search-space-set may be used as a commonsearch-space-set with index 0. The type-0 PDCCH common search-space-setmay be an common search-space-set with index 0.

A search-space-set is associated with (included in, corresponding to) acontrol resource set. The index of the control resource set associatedwith the search-space-set may be indicated by higher-layer parameters.

For a search-space-set, a part or all of 6A to 6C may be indicated atleast by higher-layer parameters. The 6A is PDCCH monitoring period. The6B is PDCCH monitoring pattern within a slot. The 6C is PDCCH monitoringoffset.

A monitoring occasion of a search-space-set may correspond to one ormore OFDM symbols in which the first OFDM symbol of the control resourceset associated with the search-space-set is allocated. A monitoringoccasion of a search-space-set may correspond to resources identified bythe first OFDM symbol of the control resource set associated with thesearch-space-set. A monitoring occasion of a search-space-set is givenbased at least on a part or all of PDCCH monitoring periodicity, PDCCHmonitoring pattern within a slot, and PDCCH monitoring offset.

FIG. 8 is a diagram showing an example of the monitoring occasion of thesearch-space-set according to an aspect of the present embodiment. InFIG. 8 , the search-space-set 91 and the search-space-set 92 are sets inthe primary cell 301, the search-space-set 93 is a set in the secondarycell 302, and the search-space-set 94 is a set in the secondary cell303.

In FIG. 8 , the block indicated by the grid line indicates thesearch-space-set 91, the block indicated by the upper right diagonalline indicates the search-space-set 92, the block indicated by the upperleft diagonal line indicates the search-space-set 93, and the blockindicated by the horizontal line indicates the search-space-set 94.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 91is set to 1 slot, the PDCCH monitoring offset for the search-space-set91 is set to 0 slot, and the PDCCH monitoring pattern for thesearch-space-set 91 is [1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 91 corresponds tothe first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDMsymbol #7) in each of the slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 92is set to 2 slots, the PDCCH monitoring offset for the search-space-set92 is set to 0 slots, and the PDCCH monitoring pattern for thesearch-space-set 92 is [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 92 corresponds tothe leading OFDM symbol (OFDM symbol #0) in each of the even slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 93is set to 2 slots, the PDCCH monitoring offset for the search-space-set93 is set to 0 slots, and the PDCCH monitoring pattern for thesearch-space-set 93 is [0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 93 corresponds tothe eighth OFDM symbol (OFDM symbol #8) in each of the even slots.

In FIG. 8 , the PDCCH monitoring periodicity for the search-space-set 94is set to 2 slots, the PDCCH monitoring offset for the search-space-set94 is set to 1 slot, and the PDCCH monitoring pattern for thesearch-space-set 94 is [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. Thatis, the monitoring occasion of the search-space-set 94 corresponds tothe leading OFDM symbol (OFDM symbol #0) in each of the odd slots.

The type-0 PDCCH common search-space-set may be at least used for a DCIformat with a cyclic redundancy check (CRC) sequence scrambled by anSI-RNTI (System Information-Radio Network Temporary Identifier).

The type-0a PDCCH common search-space-set may be used at least for a DCIformat with a cyclic redundancy check sequence scrambled by an SI-RNTI.

The type-1 PDCCH common search-space-set may be used at least for a DCIformat with a CRC sequence scrambled by an RA-RNTI (Random Access-RadioNetwork Temporary Identifier) or a CRC sequence scrambled by a TC-RNTI(Temporary Cell-Radio Network Temporary Identifier).

The type-2 PDCCH common search-space-set may be used for a DCI formatwith a CRC sequence scrambled by P-RNTI (Paging-Radio Network TemporaryIdentifier).

The type-3 PDCCH common search-space-set may be used for a DCI formatwith a CRC sequence scrambled by a C-RNTI (Cell-Radio Network TemporaryIdentifier).

The UE-specific search-space-set may be used at least for a DCI formatwith a CRC sequence scrambled by a C-RNTI.

In downlink communication, the terminal device 1 may detect a downlinkDCI format. The detected downlink DCI format is at least used forresource assignment for a PDSCH. The detected downlink DCI format isalso referred to as downlink assignment. The terminal device 1 attemptsto receive the PDSCH. Based on a PUCCH resource indicated based on thedetected downlink DCI format, an HARQ-ACK corresponding to the PDSCH(HARQ-ACK corresponding to a transport block included in the PDSCH) maybe reported to the base station device 3.

In uplink communication, the terminal device 1 may detect an uplink DCIformat. The detected uplink DCI format is at least used for resourceassignment for a PUSCH. The detected uplink DCI format is also referredto as uplink grant. The terminal device 1 transmits the PUSCH.

PUSCH transmission(s) can be dynamically scheduled by an UL grant in aDCI, or the transmission can correspond to a configured grant Type 1 orType 2. The configured grant Type 1 PUSCH transmission issemi-statically configured to operate upon the reception of higher layerparameter of configuredGrantConfig including rrc-ConfiguredUplinkGrantwithout the detection of an UL grant in a DCI. The configured grant Type2 PUSCH transmission is semi-persistently scheduled by an UL grant in avalid activation DCI according to those procedure(s) after the receptionof higher layer parameter configuredGrantConfig not includingrrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList isconfigured, more than one configured grant configuration of configuredgrant Type 1 and/or configured grant Type 2 may be active at the sametime on an active BWP of a serving cell.

More details of resource allocation in time domain for PUSCH scheduledby a DCI format is described. When the UE (terminal device 1) isscheduled to transmit a transport block and no CSI report, or the UE isscheduled to transmit a transport block and a CSI report(s) on PUSCH bya DCI, the ‘Time domain resource assignment’ field value m of the DCImay provide a row index m+1 to an allocated table. The determination ofthe used resource allocation table may be pre-defined and/or defined inRRC configuration. The indexed row of the resource allocation table maydefine the slot offset K2, the start and length indicator SLIV, ordirectly the start symbol S and the allocation length L, the PUSCHmapping type, and the number of repetitions (if RRC parameternumberOfRepetitions is present in the resource allocation table) to beapplied in the PUSCH transmission. It is noted that RRC parameter is akind of high-layer parameter.

For PUSCH scheduled by DCI format 0_1, if RRC parameterpusch-RepTypeIndicatorDCI-0-1 is set to ‘pusch-RepTypeB’, the UE mayapply PUSCH repetition Type B procedure when determining the time domainresource allocation. For PUSCH scheduled by DCI format 0_2, if RRCparameter pusch-RepTypeIndicatorDCI-0-2 is set to ‘pusch-RepTypeB’, theUE may apply PUSCH repetition Type B procedure when determining the timedomain resource allocation. Otherwise, the UE may apply PUSCH repetitionType A procedure when determining the time domain resource allocationfor PUSCH scheduled by PDCCH.

For PUSCH repetition Type A, the starting symbol S relative to the startof the slot, and the number of consecutive symbols L counting from thesymbol S allocated for the PUSCH may be determined from the start andlength indicator SLIV of the indexed row: if (L−1)≤7 thenSLIV=14(L−1)+S, otherwise SLIV=14(14−L+1+(14−1−S), where 0<L≤14−S.

For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCIformat 0_1 or 0_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI,or CS-RNTI with NDI=1, the number of repetitions K may be determined as:if RRC parameter numberOfRepetitions is present in the resourceallocation table, the number of repetitions K may be equal tonumberOfRepetitions; elseif the UE is configured with RRC parameterpusch-AggregationFactor, the number of repetitions K may be equal topusch-AggregationFactor; otherwise K=1.

If the UE is not capable of a certain coverage enhancement feature(s)(e.g. available slot based PUSCH repetition counting) or if the UE isnot provided with a certain coverage enhancement configuration(s) (e.g.available slot based PUSCH repetition counting), the following may beapplied. For PUSCH repetition Type A, in case K>1, the same symbolallocation may be applied across the K consecutive slots and the PUSCHmay be limited to a single transmission layer. The UE may repeat the TBacross the K consecutive slots applying the same symbol allocation ineach slot. The redundancy version to be applied on the nth transmissionoccasion of the TB, where n=0, 1, . . . K−1, may be determined asdescribe below. For PUSCH repetition Type A, a PUSCH transmission in aslot of a multi-slot PUSCH transmission may be omitted according to theconditions at least and/or at most in, PUSCH-priority based procedure,slot configuration based procedure, slot format based procedure andcancellation indication based procedure. For example, a slot may bedetermined as available if the slot is available according to all theconditions defined in those procedures, and/or the slot may bedetermined as not available if the slot is not available according to atleast one of the conditions defined in those procedures. K may be aninteger.

If the UE is capable of a certain coverage enhancement feature(s) and/orif the UE is provided with a certain coverage enhancementconfiguration(s), the following may be applied. For PUSCH repetitionType A, in case K>1, the same symbol allocation may be applied acrossthe K available slots (i.e. the first K slots which are available forthe PUSCH transmission) and the PUSCH may be limited to a singletransmission layer. The UE may repeat the TB across the K consecutiveslots applying the same symbol allocation in each slot. The K availableslots may be determined according to the conditions at least and/or atmost in, PUSCH-priority based procedure, slot configuration basedprocedure, slot format based procedure and cancellation indication basedprocedure. For example, a slot may be determined as available if theslot is available according to all the conditions defined in thoseprocedures, and/or the slot may be determined as not available if theslot is not available according to at least one of the conditionsdefined in those procedures.

If the UE is capable of a certain coverage enhancement feature(s) and/orif the UE is provided with a certain coverage enhancementconfiguration(s), the following may be applied. For PUSCH repetitionType A, in case K>1, the same symbol allocation may be applied acrossthe K available slots (i.e. the first K slots which are available forthe PUSCH transmission) and the PUSCH may be limited to a singletransmission layer. The UE may repeat the TB across the K availableslots applying the same symbol allocation in each slot. The K availableslots may be determined according to the conditions at least and/or atmost in first RRC parameters. The first RRC parameters may be one ormore of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated,ssb-PositionsInBurst, numberOfRepetitions,BandCombination-UplinkTxSwitch, repK, repK-RV, pusch-AggregationFactor,nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot,timeDomainAllocation, numberOfInvalidSymbolsForDL-UL-Switching,invalidSymbolPattern, and periodicityAndPattern. For PUSCH repetitionType A, a PUSCH transmission in a slot of a multi-slot PUSCHtransmission is omitted according to the conditions at least and/or atmost in second RRC parameters. The second RRC parameters may be one ormore of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated,ssb-PositionsInBurst, numberOfRepetitions,BandCombination-UplinkTxSwitch, repK, repK-RV, pusch-AggregationFactor,nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot,timeDomainAllocation, numberOfInvalidSymbolsForDL-UL-Switching,invalidSymbolPattern, and periodicityAndPattern.

The configuredGrantConfig may be referred to the ConfiguredGrantConfig.

The configuredGrantConfig may be referred to as theConfiguredGrantConfig.

When PUSCH resource allocation is semi-statically configured by higherlayer parameter configuredGrantConfig in BWP-UplinkDedicated informationelement, and the PUSCH transmission corresponding to a configured grant,the following higher layer parameters are applied in the transmission.

For Type 1 PUSCH transmissions with a configured grant, the followingparameters are given in configuredGrantConfig unless mentionedotherwise, and For the determination of the PUSCH repetition type, ifthe higher layer parameter pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured and set to ‘pusch-RepTypeB’,PUSCH repetition Type B is applied. Otherwise, PUSCH repetition Type Ais applied.

The higher layer parameter pusch-RepTypeIndicator indicates whether UEfollows the behavior for PUSCH repetition Type A or the behavior forPUSCH repetition Type B for each Type 1 configured grant configuration.The value pusch-RepTypeA enables the ‘PUSCH repetition Type A’ and thevalue pusch-RepTypeB enables the ‘PUSCH repetition Type B’. The valuepusch-RepTypeB is not configured simultaneously withcg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16.

For PUSCH repetition Type A, the selection of the time domain resourceallocation table follows the rules for DCI format 0_0 on UE specificsearch space.

For PUSCH repetition Type A, the selection of the time domain resourceallocation table is as follows. If pusch-RepTypeIndicatorDCI-0-1 inpusch-Config is configured and set to ‘pusch-RepTypeA’,pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used.Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Configis used. It is not expected that pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured with ‘pusch-RepTypeA’ when noneof pusch-RepTypeIndicatorDCI-0-1 and pusch-RepTypeIndicatorDCI-0-2 inpusch-Config is set to ‘pusch-RepTypeA’.

For PUSCH repetition Type B, the selection of the time domain resourceallocation table is as follows. If pusch-RepTypeIndicatorDCI-0-1 inpusch-Config is configured and set to ‘pusch-RepTypeB’,pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used.Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Configis used. It is not expected that pusch-RepTypeIndicator inrrc-ConfiguredUplinkGrant is configured with ‘pusch-RepTypeB’ when noneof pusch-RepTypeIndicatorDCI-0-1 and pusch-RepTypeIndicatorDCI-0-2 inpusch-Config is set to ‘pusch-RepTypeB’.

More details of resource allocation in time domain for PUSCH withconfigured grant is described. For PUSCH transmissions with a Type 1 orType 2 configured grant, the number of (nominal) repetitions K to beapplied to the transmitted transport block may be provided by theindexed row in the time domain resource allocation table ifnumberOfRepetitions is present in the table; otherwise K may be providedby the higher layer configured parameters repK. The UE may not beallowed to transmit anything on the resources configured by RRCparameter configuredGrantConfig if the higher layers did not deliver atransport block to transmit on the resources allocated for uplinktransmission without grant.

A set of allowed periodicities P are defined in RRC configuration. TheRRC parameter cg-nrofSlots, may provide the number of consecutive slotsallocated within a configured grant period. The RRC parametercg-nrofPUSCH-InSlot may provide the number of consecutive PUSCHallocations within a slot, where the first PUSCH allocation may followthe RRC parameter timeDomainAllocation for Type 1 PUSCH transmission orthe higher layer configuration according to MAC procedure, and UL grantreceived on the DCI for Type 2 PUSCH transmissions, and the remainingPUSCH allocations may have the same length and PUSCH mapping type, andmay be appended following the previous allocations without any gaps. Thesame combination of start symbol and length and PUSCH mapping type mayrepeat over the consecutively allocated slots.

The UE may not be expected to be configured with the time duration forthe transmission of K repetitions larger than the time duration derivedby the periodicity P If the UE determines that, for a transmissionoccasion, the number of symbols available for the PUSCH transmission ina slot is smaller than transmission duration L, the UE may not transmitthe PUSCH in the transmission occasion.

The procedures apply to PUSCH transmissions of PUSCH repetition Type Awith a Type 1 or Type 2 configured grant. The RRC parameter repK-RVdefines the redundancy version pattern to be applied to the repetitions.If cg-RetransmissionTimer is provided, the redundancy version for uplinktransmission with a configured grant is determined by the UE. If theparameter repK-RV is not provided in the configuredGrantConfig andcg-RetransmissionTimer is not provided, the redundancy version foruplink transmissions with a configured grant may have to be set to 0. Ifthe parameter repK-RV is provided in the configuredGrantConfig andcg-RetransmissionTimer is not provided, for the nth transmissionoccasion among K repetitions, n=1, 2, . . . , K, it is associated with(mod(n−1,4)+1)^(th) value in the configured RV sequence. If a configuredgrant configuration is configured with startingFromRV0 set to ‘off’, theinitial transmission of a transport block may only start at the firsttransmission occasion of the K repetitions. Otherwise, the initialtransmission of a transport block may start the first transmissionoccasion of the K repetitions if the configured RV sequence is{0,2,3,1}, any of the transmission occasions of the K repetitions thatare associated with RV=0 if the configured RV sequence is {0,3,0,3},and/or any of the transmission occasions of the K repetitions if theconfigured RV sequence is {0,0,0,0}, except the last transmissionoccasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting isconfigured, the initial transmission of a transport block may start atthe first transmission occasion of the K repetitions.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting is notconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 if the configured RV sequenceis {0,3,0,3}, and/or any of the transmission occasions of the Krepetitions if the configured RV sequence is {0,0,0,0}, except the lasttransmission occasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting isconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 if the configured RV sequenceis {0,3,0,3}, and/or any of the transmission occasions of the Krepetitions if the configured RV sequence is {0,0,0,0}, except the lasttransmission occasion when K≥8.

If a configured grant configuration is not configured withstartingFromRV0 set to ‘off’ and if available slot-based counting is notconfigured, the initial transmission of a transport block may start thefirst transmission occasion of the K repetitions if the configured RVsequence is {0,2,3,1}, any of the transmission occasions of the Krepetitions that are associated with RV=0 assuming the transmissionoccasions of the K repetitions are determined based on consecutivephysical slots if the configured RV sequence is {0,3,0,3}, and/or any ofthe transmission occasions of the K repetitions if the configured RVsequence is {0,0,0,0}, except the last transmission occasion when K≥8.

For any RV sequence, the repetitions may have to be terminated aftertransmitting K repetitions, or at the last transmission occasion amongthe K repetitions within the period P, or from the starting symbol ofthe repetition that overlaps with a PUSCH with the same HARQ processscheduled by DCI format 0_0, 0_1 or 0_2, whichever is reached first. Inaddition, the UE may have to terminate the repetition of a transportblock in a PUSCH transmission if the UE receives a DCI format 0_1 withDFI flag provided and set to ‘1’, and if in this DCI the UE detects ACKfor the HARQ process corresponding to that transport block.

The UE is not expected to be configured with the time duration for thetransmission of K repetitions larger than the time duration derived bythe periodicity P. If the UE determines that, for a transmissionoccasion, the number of symbols available for the PUSCH transmission ina slot is smaller than transmission duration L, the UE does not transmitthe PUSCH in the transmission occasion.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isenabled, the UE determines N*K slots for a PUSCH transmission of a PUSCHrepetition Type A, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst. A slot is not counted in the number of N*K slotsfor PUSCH transmission of a PUSCH repetition Type A if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst. Otherwise, the UE determines N*K consecutive slotsfor a PUSCH transmission of a PUSCH repetition Type A. For the case ofreduced capability half-duplex UE, and when AvailableSlotCounting isenabled, a slot is not counted in the number of N*K slots for a PUSCHtransmission of a PUSCH repetition Type A, if at least one of thesymbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a symbol of an SS/PBCH block with indexprovided by ssb-PositionsInBurst.

For paired spectrum and SUL band, The UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition type A,irrespective of whether AvailableSlotCounting is enabled or not. For thecase of reduced capability half-duplex UE, and whenAvailableSlotCounting is enabled, a slot is not counted in the number ofN*K slots for a PUSCH transmission of a PUSCH repetition Type A, if atleast one of the symbols indicated by the indexed row of the usedresource allocation table in the slot overlaps with a symbol of anSS/PBCH block with index provided by ssb-PositionsInBurst.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for unpaired spectrum, if an RRC parameterAvailableSlotCounting is enabled, the UE may have to repeat the TBacross the N*K slots determined for the PUSCH transmission applying thesame symbol allocation in each slot. Otherwise, the UE may have torepeat the TB across the N*K consecutive slots applying the same symbolallocation in each slot, except if the UE is provided with higher layerparameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UErepeats the TB in the repK earliest consecutive transmission occasioncandidates within the same configuration.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for paired spectrum, irrespective of whetherAvailableSlotCounting is enabled or not, the UE may have to repeat theTB across the N*K consecutive slots applying the same symbol allocationin each slot, except if the UE is provided with higher layer parameterscg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats theTB in the repK earliest consecutive transmission occasion candidateswithin the same configuration. A Type 1 or Type 2 PUSCH transmissionwith a configured grant in a slot is omitted according to the conditionsin the UE procedure(s) for reporting control information, the UEprocedure(s) for determining slot configuration(s) and the UEprocedure(s) associated with cancellation indication.

If the available slot based counting is not configured [or for pairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK consecutive slots applying the same symbol allocation in each slot,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

If the available slot based counting is configured [and for unpairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across thefirst K available slots applying the same symbol allocation in each slotwhere each of the available slots is a slot having an UL symbol, asdescribed in the UE procedure(s) for determining slot configuration(s),or flexible symbol, as described in the UE procedure(s) for determiningslot configuration(s), that is not SS/PBCH block symbol, for the PUSCH,and[/or] consecutive UL symbols, as described in the UE procedure(s) fordetermining slot configuration(s), or flexible symbols, as described inthe UE procedure(s) for determining slot configuration(s), that are notSS/PBCH block symbols, starting from the first symbol, equal to orlarger than a number of symbols for the PUSCH, except if the UE isprovided with higher layer parameters cg-nrofSlots andcg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration. A Type 1 or Type 2 PUSCH transmission with a configuredgrant in a slot is omitted according to the conditions in the UEprocedure(s) for reporting control information, the UE procedure(s) fordetermining slot configuration(s) and the UE procedure(s) associatedwith cancellation indication. A SS/PBCH block symbol is a symbol of anSS/PBCH block with candidate SS/PBCH block index corresponding to theSS/PBCH block index indicated to a UE by ssb-PositionsInBurst in SIB1 orssb-PositionsInBurst in ServingCellConfigCommon, as described in the UEsynchronization procedure for searching a cell.

If available slot based counting is not configured [or for pairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK consecutive slots applying the same symbol allocation in each slot,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

If available slot based counting is configured [and for unpairedspectrum], for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across aninitial slot and the following K−1 available slots applying the samesymbol allocation in each slot where the initial slot is a slot havingthe symbol defined in the uplink transmission procedure(s) withoutdynamic grant by the MAC entity and each of the available slots is aslot having an UL symbol, as described in the UE procedure(s) fordetermining slot configuration(s), or flexible symbol, as described inthe UE procedure(s) for determining slot configuration(s), that is notSS/PBCH block symbol, for the PUSCH, and/or consecutive UL symbols, asdescribed in the UE procedure(s) for determining slot configuration(s),or flexible symbols, as described in the UE procedure(s) for determiningslot configuration(s), that are not SS/PBCH block symbols, starting fromthe first symbol, equal to or larger than a number of symbols for thePUSCH, except if the UE is provided with higher layer parameterscg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats theTB in the repK earliest consecutive transmission occasion candidateswithin the same configuration. A Type 1 or Type 2 PUSCH transmissionwith a configured grant in a slot is omitted according to the conditionsin the UE procedure(s) for reporting control information, the UEprocedure(s) for determining slot configuration(s) and the UEprocedure(s) associated with cancellation indication. A SS/PBCH blocksymbol is a symbol of an SS/PBCH block with candidate SS/PBCH blockindex corresponding to the SS/PBCH block index indicated to a UE byssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst inServingCellConfigCommon, as described in the UE synchronizationprocedure for searching a cell.

The MAC entity may be included in the medium access control layerprocessing unit 15.

The UE may not expect that the initial slot is not available.

If the available slot-based counting is not configured or for pairedspectrum, for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK consecutive slots applying the same symbol allocation in each slot,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

If the available slot-based counting is configured and for unpairedspectrum, for both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may have to repeat the TB across theK available slots applying the same symbol allocation in each slot whereeach of the available slots is a slot having an UL symbol, as describedin those procedures, or flexible symbol, according to the conditions inthose procedures, that is not SS/PBCH block symbol, for the PUSCH,and/or consecutive UL symbols, according to the conditions in thoseprocedures, or flexible symbols, according to the conditions in thoseprocedures, that are not SS/PBCH block symbols, starting from the firstsymbol, equal to or larger than a number of symbols for the PUSCH,except if the UE is provided with higher layer parameters cg-nrofSlotsand cg-nrofPUSCH-InSlot, in which case the UE repeats the TB in the repKearliest consecutive transmission occasion candidates within the sameconfiguration.

A Type 1 or Type 2 PUSCH transmission with a configured grant in a slotis omitted according to the conditions in those procedures. An SS/PBCHblock symbol is a symbol of an SS/PBCH block with candidate SS/PBCHblock index corresponding to the SS/PBCH block index indicated to a UEby ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst inServingCellConfigCommon, according to the conditions in thoseprocedures.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, the UE may have to repeat the TB across the K consecutiveslots applying the same symbol allocation in each slot, except if the UEis provided with RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, inwhich case the UE repeats the TB in the repK earliest consecutivetransmission occasion candidates within the same configuration. A Type 1or Type 2 PUSCH transmission with a configured grant in a slot isomitted according to the conditions in one or more RRC configurations.

The procedures apply to PUSCH transmissions of PUSCH repetition Type Bwith a Type 1 or Type 2 configured grant. For PUSCH transmissions with aType 1 or Type 2 configured grant, the nominal repetitions and theactual repetitions are determined according to the procedures for PUSCHrepetition Type B according to at least one of defined in thoseprocedures. The higher layer configured parameters repK-RV defines theredundancy version pattern to be applied to the repetitions. If theparameter repK-RV is not provided in the configuredGrantConfig, theredundancy version for each actual repetition with a configured grantmay have to be set to 0. Otherwise, for the nth transmission occasionamong all the actual repetitions (including the actual repetitions thatare omitted) of the K nominal repetitions, it is associated with(mod(n−1,4)+1)^(th) value in the configured RV sequence. If a configuredgrant configuration is configured with startingFromRV0 set to ‘off’, theinitial transmission of a transport block may only start at the firsttransmission occasion of the actual repetitions. Otherwise, the initialtransmission of a transport block may start at the first transmissionoccasion of the actual repetitions if the configured RV sequence is{0,2,3,1}, any of the transmission occasions of the actual repetitionsthat are associated with RV=0 if the configured RV sequence is{0,3,0,3}, and/or any of the transmission occasions of the actualrepetitions if the configured RV sequence is {0,0,0,0}, except theactual repetitions within the last nominal repetition when K≥8.

For any RV sequence, the repetitions may have to be terminated aftertransmitting K nominal repetitions, or at the last transmission occasionamong the K nominal repetitions within the period P, or from thestarting symbol of a repetition that overlaps with a PUSCH with the sameHARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever isreached first. The UE is not expected to be configured with the timeduration for the transmission of K nominal repetitions larger than thetime duration derived by the periodicity P.

For PUSCH repetition Type A (as determined according to proceduresdefined in those procedures for scheduled PUSCH, or those procedures forconfigured PUSCH), a UE is configured for frequency hopping by the RRCparameter frequencyHoppingDCI-0-1 (e.g. frequencyHoppingDCI-0-1-r16and/or frequencyHoppingDCI-0-1-r17) in pusch-Config for PUSCHtransmission scheduled by DCI format 0_1, and frequencyHoppingDCI-0-2 inpusch-Config for PUSCH transmission scheduled by DCI format 0_2, and byfrequencyHopping provided in pusch-Config for PUSCH transmissionscheduled by a DCI format other than 0_2, and by frequencyHoppingprovided in configuredGrantConfig for configured PUSCH transmission, andby frequencyHoppingPUSCH-RepTypeA provided in rrc-ConfiguredUplinkGrantfor Type 1 configured PUSCH transmission. One of two frequency hoppingmodes (intra-slot frequency hopping, applicable to single slot andmulti-slot PUSCH transmission and inter-slot frequency hopping,applicable to multi-slot PUSCH transmission) can be configured. Onefrequency hopping mode can be further configured (inter-repetitionfrequency hopping, applicable to multi-slot PUSCH transmission).

The pusch-Config may be referred to the PUSCH-Config.

The pusch-Config may be referred to as the PUSCH-Config.

The RRC parameter frequencyHopping indicates that the value intraSlotenables ‘Intra-slot frequency hopping’ and the value interSlot enables‘Inter-slot frequency hopping’. If the field is absent, frequencyhopping is not configured for ‘pusch-RepTypeA’. The fieldfrequencyHopping applies to DCI format 0_0 and 0_1 for ‘pusch-RepTypeA’.

The RRC parameter frequencyHoppingDCI-0-1-r16 indicates the frequencyhopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 isset to ‘pusch-RepTypeB’, The value interRepetition enables‘Inter-repetition frequency hopping’, and the value interSlot enables‘Inter-slot frequency hopping’. If the field is absent, frequencyhopping is not configured for DCI format 0_1.

The RRC parameter frequencyHoppingDCI-0-1-r17 indicates the frequencyhopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 isset to ‘pusch-RepTypeA’ or ‘pusch-RepTypeB’ with ‘Inter-repetitionfrequency hopping’. The value interRepetition enables ‘Inter-repetitionfrequency hopping’, and the value interSlot enables ‘Inter-slotfrequency hopping’, and the value intraSlot enables ‘intra-slotfrequency hopping’. If the field is absent, inter-repetition frequencyhopping is not configured for DCI format 0_1 for ‘pusch-RepTypeA’ andfrequency hopping is not configured for DCI format 01 for‘pusch-RepTypeB’. Or the RRC parameter frequencyHoppingDCI-0-1-r17 mayindicate the frequency hopping scheme for DCI format 0_1 whenpusch-RepTypeIndicatorDCI-0-1 is set to ‘pusch-RepTypeA’ enabling‘Inter-repetition frequency hopping’.

In case of resource allocation type 2, the UE transmits PUSCH withoutfrequency hopping.

In case of resource allocation type 1, whether or not transformprecoding is enabled for PUSCH transmission, the UE may perform PUSCHfrequency hopping, if the frequency hopping field in a correspondingdetected DCI format or in a random access response UL grant is set to 1,or if for a Type 1 PUSCH transmission with a configured grant the RRCparameter frequencyHoppingOffset is provided, otherwise no PUSCHfrequency hopping is performed. When frequency hopping is enabled forPUSCH, the RE mapping is defined in those procedures.

For a PUSCH scheduled by RAR UL grant, fallbackRAR UL grant, or by DCIformat 0_0 with CRC scrambled by TC-RNTI, frequency offsets are obtainedas described in those procedures. For a PUSCH scheduled by DCI format0_0/0_1 or a PUSCH based on a Type2 configured UL grant activated by DCIformat 0_0/0_1 and for resource allocation type 1, frequency offsets areconfigured by RRC parameter frequencyHoppingOffsetLists in pusch-Config.For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type2configured UL grant activated by DCI format 0_2 and for resourceallocation type 1, frequency offsets are configured by RRC parameterfrequencyHoppingOffsetListsDCI-0-2 in pusch-Config. When the size of theactive BWP is less than 50 PRBs, one of two higher layer configuredoffsets is indicated in the UL grant. When the size of the active BWP isequal to or greater than 50 PRBs, one of four higher layer configuredoffsets is indicated in the UL grant.

For PUSCH based on a Type1 configured UL grant the frequency offset isprovided by the RRC parameter frequencyHoppingOffset inrrc-ConfiguredUplinkGrant.

For PUSCH repetition Type B (as determined according to proceduresdefined in those procedures for scheduled PUSCH, or those procedures forconfigured PUSCH), a UE is configured for frequency hopping by the RRCparameter frequencyHoppingDCI-0-2 in pusch-Config for PUSCH transmissionscheduled by DCI format 0_2, by frequencyHoppingDCI-0-1 provided inpusch-Config for PUSCH transmission scheduled by DCI format 0_1, and byfrequencyHoppingPUSCH-RepTypeB provided in rrc-ConfiguredUplinkGrant forType 1 configured PUSCH transmission. The frequency hopping mode forType 2 configured PUSCH transmission follows the configuration of theactivating DCI format. One of two frequency hopping modes(Inter-repetition frequency hopping and Inter-slot frequency hopping)can be configured.

In case of resource allocation type 1, whether or not transformprecoding is enabled for PUSCH transmission, the UE may perform PUSCHfrequency hopping, if the frequency hopping field in a correspondingdetected DCI format is set to 1, or if for a Type 1 PUSCH transmissionwith a configured grant the RRC parameter frequencyHoppingPUSCH-RepTypeBis provided, otherwise no PUSCH frequency hopping is performed. Whenfrequency hopping is enabled for PUSCH, the RE mapping is defined inthose procedures.

For a PUSCH scheduled by DCI format 0_1 or a PUSCH based on a Type 2configured UL grant activated by DCI format 0_1 and for resourceallocation type 1, frequency offsets are configured by RRC parameterfrequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled byDCI format 0_2 or a PUSCH based on a Type 2 configured UL grantactivated by DCI format 0_2 and for resource allocation type 1,frequency offsets are configured by RRC parameterfrequencyHoppingOffsetListsDCI-0-2 in pusch-Config. When the size of theactive BWP is less than 50 PRBs, one of two higher layer configuredoffsets is indicated in the UL grant. When the size of the active BWP isequal to or greater than 50 PRBs, one of four higher layer configuredoffsets is indicated in the UL grant.

For PUSCH based on a Type1 configured UL grant the frequency offset isprovided by the RRC parameter frequencyHoppingOffset inrrc-ConfiguredUplinkGrant.

In case of inter-slot frequency hopping, the starting RB during slotn{circumflex over ( )}u_s follows that of inter-slot frequency hoppingfor PUSCH Repetition Type A according to at least one of the conditionsdefined in those procedures.

If the UE is not capable of a certain coverage enhancement feature(s)(e.g. available slot based PUSCH repetition counting) or if the UE isnot provided with a certain coverage enhancement configuration(s) (e.g.available slot based PUSCH repetition counting), the following (i.e. thenumber of repetitions counted based on contiguous (or continuous, orconsecutive) slots) may be applied. Alternatively or additionally, ifthe UE is capable of a certain coverage enhancement feature(s) and ifthe UE is provided with a slot-counting type configuration (the RRCconfiguration or RRC parameter for indicating whether the number ofrepetitions are counted based on contiguous (or continuous) slots orbased on available slots) which indicates the PUSCH repetition to becounted based on contiguous slots, the following may be applied. Forboth Type 1 and Type 2 PUSCH transmissions with a configured grant, whenK>1, the UE may repeat the TB across the K consecutive slots applyingthe same symbol allocation in each slot, except if the UE is providedwith RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which casethe UE may repeat the TB in the repK earliest consecutive transmissionoccasion candidates within the same configuration. A Type 1 or Type 2PUSCH transmission with a configured grant in a slot may be omittedaccording to the conditions at least and/or at most in, PUSCH-prioritybased procedure, slot configuration based procedure, slot format basedprocedure and cancellation indication based procedure. For example, aslot may be determined as available if the slot is available accordingto all the conditions defined in those procedures, and/or the slot maybe determined as not available if the slot is not available according toat least one of the conditions defined in those procedures.

It is noted that the aforementioned slot-counting type configuration maybe referred to as a different name. The existence of the slot-countingtype configuration in RRC configuration message may mean that the numberof repetitions is counted based on available slots while the absence ofthe slot-counting type configuration in RRC configuration message maymean that the number of repetitions is counted based on contiguousslots. Additionally and/or alternatively, the slot-counting typeconfiguration set to the first value (e.g. ‘contiguous’) may mean thatthe number of repetitions is counted based on contiguous slots while theslot-counting type configuration set to the second value (e.g.‘available’) may mean that the number of repetitions is counted based onavailable slots.

If the UE is capable of a certain coverage enhancement feature(s) and/orif the UE is provided with a certain coverage enhancementconfiguration(s), the following (i.e. the number of repetitions countedbased on available slots) may be applied. Alternatively or additionally,if the UE is capable of a certain coverage enhancement feature(s) and ifthe UE is provided with a slot-counting type configuration whichindicates the PUSCH repetition to be counted based on available slots,the following may be applied. For both Type 1 and Type 2 PUSCHtransmissions with a configured grant, when K>1, the UE may repeat theTB across the K available slots (i.e. the first K slots which areavailable for the PUSCH transmission) applying the same symbolallocation in each slot. The K available slots may be determinedaccording to the conditions at least and/or at most in, PUSCH-prioritybased procedure, slot configuration based procedure, slot format basedprocedure and cancellation indication based procedure. For example, aslot may be determined as available if the slot is available accordingto all the conditions defined in those procedures, and/or the slot maybe determined as not available if the slot is not available according toat least one of the conditions defined in those procedures.

The pattern of inter-slot frequency hopping according to the availableslots may be determined based on the omission of PUSCH transmissions.

The pattern of RV according to the available slots may be determinedbased on the omission of PUSCH transmissions.

The pattern of slot-counting according to the available slots may bedetermined based on the omission of PUSCH transmissions.

The PUSCH-priority based procedure is described. If a PUSCH is scheduledby a DCI or a PUSCH with configured grant is configured, the PUSCH istransmitted unless otherwise stated.

A PUSCH or a PUCCH transmission, including repetitions if any, can be ofpriority index 0 or of priority index 1. For a configured grant PUSCHtransmission, a UE may determine a priority index from RRC parameterphy-PriorityIndex, if provided. For a PUCCH transmission with HARQ-ACKinformation corresponding to a SPS PDSCH reception or a SPS PDSCHrelease, a UE may determine a priority index from RRC parameterharq-CodebookID, if provided. For a PUCCH transmission with SR, a UE maydetermine the corresponding priority by RRC parameter phy-PriorityIndexin RRC parameter SchedulingRequestResourceConfig, if any. For a PUSCHtransmission with semi-persistent CSI report, a UE may determine apriority index from a priority indicator field, if provided, in a DCIformat that activates the semi-persistent CSI report. If a priorityindex is not provided to a UE for a PUSCH or a PUCCH transmission, thepriority index may be 0.

If in an active DL BWP a UE may monitor PDCCH either for detection ofDCI format 0_1 and DCI format 1_1 or for detection of DCI format 0_2 andDCI format 1_2, a priority index can be provided by a priority indicatorfield. If a UE indicates a capability to monitor, in an active DL BWP,PDCCH for detection of DCI format 0_1 and DCI format 1_1 and fordetection of DCI format 0_2 and DCI format 1_2, a DCI format 0_1 or aDCI format 0_2 can schedule a PUSCH transmission of any priority and aDCI format 1_1 or a DCI format 1_2 can schedule a PDSCH reception andtrigger a PUCCH transmission with corresponding HARQ-ACK information ofany priority.

When a UE determines overlapping for PUCCH and/or PUSCH transmissions ofdifferent priority indexes, including repetitions if any, the UE mayfirst resolve the overlapping for PUCCH and/or PUSCH transmissions ofsmaller priority index. Then: if a transmission of a first PUCCH oflarger priority index scheduled by a DCI format in a PDCCH receptionwould overlap in time with a repetition of a transmission of a secondPUSCH or a second PUCCH of smaller priority index, the UE may cancel therepetition of a transmission of the second PUSCH or the second PUCCHbefore the first symbol that would overlap with the first PUCCHtransmission; if a transmission of a first PUSCH of larger priorityindex scheduled by a DCI format in a PDCCH reception would overlap intime with a repetition of the transmission of a second PUCCH of smallerpriority index, the UE may cancel the repetition of the transmission ofthe second PUCCH before the first symbol that would overlap with thefirst PUSCH transmission. The overlapping may be applicable before orafter resolving overlapping among channels of larger priority index, ifany. The UE may expect that the transmission of the first PUCCH or thefirst PUSCH, respectively, would not start before T_(proc,2)+d_1 after alast symbol of the corresponding PDCCH reception. T_(proc,2) is thePUSCH preparation time for a corresponding UE processing capabilityassuming d_2,1=0, based on p and N_2, and d_1 is determined by areported UE capability.

If the slot-counting type configuration indicates that the number ofrepetitions to be counted based on contiguous slots, the above-describedprocessing time requirement that the first PUSCH would not start beforeT_(proc,2)+d_1 after a last symbol of the corresponding PDCCH receptionmay be applied. If the slot-counting type configuration indicates thatthe number of repetitions to be counted based on available slots, theprocessing time requirement may be relaxed. For example, the processingtime requirement that the first PUSCH would not start beforeT_(proc,2)+d_1+d_x after a last symbol of the corresponding PDCCHreception may be applied, where d_x is a positive value. The d_x may beexpressed in unit of symbols. In other words, If the number ofrepetitions for PUSCH repetition Type A is counted based on contiguousslots, the processing time requirement that the first PUSCH would notstart before T_(proc,2)+d_1 after a last symbol of the correspondingPDCCH reception may be applied. If the number of repetitions for PUSCHrepetition Type A is counted based on available slots, the processingtime requirement may be relaxed. The relaxation of the processing timerequirement may mean allowing longer gap duration between PUSCH startand the end of the corresponding PDCCH, where the processing timerequirement may be the maximum processing time which is required forcancellation of a scheduled/configured/granted PUSCH transmission.

If a UE is scheduled by a DCI format in a first PDCCH reception totransmit a first PUCCH or a first PUSCH of larger priority index thatoverlaps with a second PUCCH or a second PUSCH transmission of smallerpriority index that, if any, is scheduled by a DCI format in a secondPDCCH, T_(proc,2) may be based on a value of p corresponding to thesmallest SCS configuration of the first PDCCH, the second PDCCHs, thefirst PUCCH or the first PUSCH, and the second PUCCHs or the secondPUSCHs. If the overlapping group includes the first PUCCH, N_2 is 5 forμ=0, 5.5 for μ=1 and 11 for μ=2 if RRC parameter processingType2Enabledof RRC parameter PDSCH-ServingCellConfig is set to enable for theserving cell where the UE receives the first PDCCH and for all servingcells where the UE receives the PDSCHs corresponding to the secondPUCCHs, and if processingType2Enabled of RRC parameterPUSCH-ServingCellConfig is set to enable for the serving cells with thesecond PUSCHs, N_2 is 10 for μ=0, 12 for μ=1, 23 for μ=2, and 36 for μ=3otherwise. If the overlapping group includes the first PUSCH, N_2 is 5for μ=0, 5.5 for μ=1 and 11 for μ=2 if processingType2Enabled ofPUSCH-ServingCellConfig is set to enable for the serving cells with thefirst PUSCH and the second PUSCHs and if processingType2Enabled ofPDSCH-ServingCellConfig is set to enable for all serving cells where theUE receives the PDSCHs corresponding to the second PUCCHs, N_2 is 10 forμ=0, 12 for μ=1, 23 for μ=2, and 36 for μ=3 otherwise.

If a UE would transmit the following channels, including repetitions ifany, that would overlap in time: a first PUCCH of larger priority indexwith SR and a second PUCCH or PUSCH of smaller priority index; or aconfigured grant PUSCH of larger priority index and a PUCCH of smallerpriority index; or a first PUCCH of larger priority index with HARQ-ACKinformation only in response to a PDSCH reception without acorresponding PDCCH and a second PUCCH of smaller priority index with SRand/or CSI, or a configured grant PUSCH with smaller priority index, ora PUSCH of smaller priority index with SP-CSI report(s) without acorresponding PDCCH; or a PUSCH of larger priority index with SP-CSIreports(s) without a corresponding PDCCH and a PUCCH of smaller priorityindex with SR, or CSI, or HARQ-ACK information only in response to aPDSCH reception without a corresponding PDCCH; or a configured grantPUSCH of larger priority index and a configured PUSCH of lower priorityindex on a same serving cell, the UE may be expected to cancel arepetition of the PUCCH/PUSCH transmissions of smaller priority indexbefore the first symbol overlapping with the PUCCH/PUSCH transmission oflarger priority index if the repetition of the PUCCH/PUSCH transmissionsof smaller priority index overlaps in time with the PUCCH/PUSCHtransmissions of larger priority index.

A UE may not expect to be scheduled to transmit a PUCCH or a PUSCH withsmaller priority index that would overlap in time with a PUCCH of largerpriority index with HARQ-ACK information only in response to a PDSCHreception without a corresponding PDCCH. A UE may not expect to bescheduled to transmit a PUCCH of smaller priority index that wouldoverlap in time with a PUSCH of larger priority index with SP-CSIreport(s) without a corresponding PDCCH.

If a UE multiplexes aperiodic CSI in a PUSCH and the UE would multiplexUCI that includes HARQ-ACK information in a PUCCH that overlaps with thePUSCH and the timing conditions for overlapping PUCCHs and PUSCHs arefulfilled, the UE may multiplex only the HARQ-ACK information in thePUSCH and does not transmit the PUCCH.

If a UE transmits multiple PUSCHs in a slot on respective serving cellsthat include first PUSCHs that are scheduled by DCI formats and secondPUSCHs configured by respective RRC parameter ConfiguredGrantConfig orsemiPersistentOnPUSCH, and the UE would multiplex UCI in one of themultiple PUSCHs, and the multiple PUSCHs fulfil the conditions for UCImultiplexing, the UE may multiplex the UCI in a PUSCH from the firstPUSCHs.

If a UE transmits multiple PUSCHs in a slot on respective serving cellsand the UE would multiplex UCI in one of the multiple PUSCHs and the UEdoes not multiplex aperiodic CSI in any of the multiple PUSCHs, the UEmay multiplex the UCI in a PUSCH of the serving cell with the smallestRRC parameter ServCellIndex subject to the conditions for UCImultiplexing being fulfilled. If the UE transmits more than one PUSCHsin the slot on the serving cell with the smallest ServCellIndex thatfulfil the conditions for UCI multiplexing, the UE may multiplex the UCIin the earliest PUSCH that the UE transmits in the slot.

If a UE transmits a PUSCH over multiple slots and the UE would transmita PUCCH with HARQ-ACK and/or CSI information over a single slot thatoverlaps with the PUSCH transmission in one or more slots of themultiple slots, and the PUSCH transmission in the one or more slotsfulfills the conditions for multiplexing the HARQ-ACK and/or CSIinformation, the UE may multiplex the HARQ-ACK and/or CSI information inthe PUSCH transmission in the one or more slots. The UE may notmultiplex HARQ-ACK and/or CSI information in the PUSCH transmission in aslot from the multiple slots if the UE would not transmit a single-slotPUCCH with HARQ-ACK and/or CSI information in the slot in case the PUSCHtransmission was absent.

If the PUSCH transmission over the multiple slots is scheduled by a DCIformat that includes a DAI field, the value of the DAI field may beapplicable for multiplexing HARQ-ACK information in the PUSCHtransmission in any slot from the multiple slots where the UEmultiplexes HARQ-ACK information.

When a UE would multiplex HARQ-ACK information in a PUSCH transmissionthat is configured by an RRC parameter ConfiguredGrantConfig, andincludes CG-UCI, the UE may multiplex the HARQ-ACK information in thePUSCH transmission if the UE is provided RRC parametercg-UCI-Multiplexing; otherwise, the UE does not transmit the PUSCH andmultiplexes the HARQ-ACK information in a PUCCH transmission or inanother PUSCH transmission.

If a PUSCH (or a repetition of a PUSCH) in a slot is determined to betransmitted or to multiplex UCI(s), the slot may be considered asavailable for the PUSCH transmission. If a PUSCH (or a repetition of aPUSCH) in a slot is determined to be cancelled, the slot may beconsidered as not available for the PUSCH transmission.

The slot configuration based procedure is described. If a PUSCH isscheduled by a DCI or a PUSCH with configured grant is configured, thePUSCH is transmitted unless otherwise stated.

If a UE is provided RRC parameter tdd-UL-DL-ConfigurationCommon, the UEmay set the slot format (the format which indicates which type of symbolbetween downlink, uplink and flexible symbols each symbol in a slot is)per slot over a number of slots as indicated bytdd-UL-DL-ConfigurationCommon. If the UE is additionally provided RRCparameter tdd-UL-DL-ConfigurationDedicated, the parametertdd-UL-DL-ConfigurationDedicated may override only flexible symbols perslot over the number of slots as provided bytdd-UL-DL-ConfigurationCommon.

For operation on a single carrier in unpaired spectrum, if a UE isconfigured by higher layers to receive a PDCCH, or a PDSCH, or a CSI-RS,or a DL PRS in a set of symbols of a slot, the UE receives the PDCCH,the PDSCH, the CSI-RS, or the DL PRS if the UE does not detect a DCIformat that indicates to the UE to transmit a PUSCH, a PUCCH, a PRACH,or a SRS in at least one symbol of the set of symbols of the slot;otherwise, the UE may not receive the PDCCH, or the PDSCH, or theCSI-RS, or the DL PRS in the set of symbols of the slot.

For operation on a single carrier in unpaired spectrum, if a UE isconfigured by higher layers to transmit SRS, or PUCCH, or PUSCH, orPRACH in a set of symbols of a slot and the UE detects a DCI formatindicating to the UE to receive CSI-RS or PDSCH in a subset of symbolsfrom the set of symbols, then: the following A), B) and C) may beapplied. A) If the UE does not indicate the capability ofpartialCancellation, the UE does not expect to cancel the transmissionof the PUCCH or PUSCH or PRACH in the set of symbols if the first symbolin the set occurs within T_(proc,2) relative to a last symbol of aCORESET where the UE detects the DCI format; otherwise, the UE cancelsthe PUCCH, or the PUSCH, or an actual repetition of the PUSCH, or thePRACH transmission in the set of symbols. B) If the UE indicates thecapability of partialCancellation, the UE does not expect to cancel thetransmission of the PUCCH or PUSCH or PRACH in symbols from the set ofsymbols that occur within T_(proc,2) relative to a last symbol of aCORESET where the UE detects the DCI format. The UE cancels the PUCCH,or the PUSCH, or an actual repetition of the PUSCH, or the PRACHtransmission in remaining symbols from the set of symbols. C) The UEdoes not expect to cancel the transmission of SRS in symbols from thesubset of symbols that occur within T_(proc,2) relative to a last symbolof a CORESET where the UE detects the DCI format. The UE cancels the SRStransmission in remaining symbols from the subset of symbols. T_(proc,2)is the PUSCH preparation time for the corresponding UE processingcapability assuming d_2,1=1 and p corresponds to the smallest SCSconfiguration between the SCS configuration of the PDCCH carrying theDCI format and the SCS configuration of the SRS, PUCCH, PUSCH or μ_r,where μ_r corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise μ_r=0.

If the slot-counting type configuration indicates that the number ofrepetitions to be counted based on contiguous slots, the above-describedprocessing time requirement that “UE does not expect to cancel thetransmission of the PUSCH in the set of symbols if the first symbol inthe set occurs within T_(proc,2) relative to a last symbol of a CORESETwhere the UE detects the DCI format, otherwise UE cancels the PUSCHtransmission” may be applied. If the slot-counting type configurationindicates that the number of repetitions to be counted based onavailable slots, the processing time requirement may be relaxed. Forexample, “UE does not expect to cancel the transmission of the PUSCH inthe set of symbols if the first symbol in the set occurs withinT_(proc,2)+d_x relative to a last symbol of a CORESET where the UEdetects the DCI format, otherwise UE cancels the PUSCH transmission” maybe applied, where d_x is a positive value. In other words, If the numberof repetitions for PUSCH repetition Type A is counted based oncontiguous slots, the processing time requirement of T_(proc,2) may beapplied. If the number of repetitions for PUSCH repetition Type A iscounted based on available slots, the longer processing time requirementmay be applied.

For a set of symbols of a slot that are indicated to a UE as downlink bytdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, theUE may not transmit PUSCH, PUCCH, PRACH, or SRS when the PUSCH, PUCCH,PRACH, or SRS overlaps, even partially, with the set of symbols of theslot.

For a set of symbols of a slot that are indicated to a UE as flexible bytdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated ifprovided, the UE may not expect to receive both dedicated RRC parametersconfiguring transmission from the UE in the set of symbols of the slotand dedicated RRC parameters configuring reception by the UE in the setof symbols of the slot.

For operation on a single carrier in unpaired spectrum, for a set ofsymbols of a slot indicated to a UE by RRC parameterssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst inServingCellConfigCommon, for reception of SS/PBCH blocks, the UE may nottransmit PUSCH, PUCCH, PRACH in the slot if a transmission would overlapwith any symbol from the set of symbols and the UE does not transmit SRSin the set of symbols of the slot. The UE may not expect the set ofsymbols of the slot to be indicated as uplink bytdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, whenprovided to the UE.

If a UE is scheduled by a DCI format to transmit PUSCH over multipleslots, and if tdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicated, indicates that, for a slot from themultiple slots, at least one symbol from a set of symbols where the UEis scheduled PUSCH transmission in the slot is a downlink symbol, the UEmay not transmit the PUSCH in the slot.

If a PUSCH (or a repetition of a PUSCH) in a slot is determined to betransmitted, the slot may be considered as available for the PUSCHtransmission. If a PUSCH (or a repetition of a PUSCH) in a slot isdetermined to be cancelled or not to be transmitted, the slot may beconsidered as not available for the PUSCH transmission.

An example of the definition of T_(proc,2) is described. If the firstuplink symbol in the PUSCH allocation for a transport block, includingthe DM-RS, as defined by the slot offset K2 and the start S and length Lof the PUSCH allocation indicated by ‘Time domain resource assignment’of the scheduling DCI and including the effect of the timing advance, isno earlier than at symbol L2, where L2 is defined as the next uplinksymbol with its CP starting T_(proc,2)(T_(proc,2)=max((N₂+d_(2,1)+d₂)(2048+144)·κ2^(−μ)·T_(c)+T_(ext)+T_(switch),d_(2,2)))after the end of the reception of the last symbol of the PDCCH carryingthe DCI scheduling the PUSCH, then the UE may transmit the transportblock. N2 is based on μ for UE processing capability 1 and 2respectively, where μ corresponds to the one of (μDL, μUL) resultingwith the largest T_(proc,2), where the μDL corresponds to the subcarrierspacing of the downlink with which the PDCCH carrying the DCI schedulingthe PUSCH was transmitted and μUL corresponds to the subcarrier spacingof the uplink channel with which the PUSCH is to be transmitted, and theconstant κ is 64. For operation with shared spectrum channel access,T_ext may be non-zero value, otherwise T_ext=0. If the first symbol ofthe PUSCH allocation consists of DM-RS only, then d2,1=0, otherwised2,1=1. The time units T_C=1/(Δf_“max” N_f) whereΔf_“max”=480·10{circumflex over ( )}3 Hz and N_f=4096. If the UE isconfigured with multiple active component carriers, the first uplinksymbol in the PUSCH allocation further includes the effect of timingdifference between component carriers. If the scheduling DCI triggered aswitch of BWP, d2,2 equals to the switching time, otherwise d2,2=0. If aPUSCH of a larger priority index would overlap with PUCCH of a smallerpriority index, d2 for the PUSCH of a larger priority is set as reportedby the UE; otherwise d2=0. For a UE that supports capability 2 on agiven cell, the processing time according to UE processing capability 2is applied if the high layer parameter processingType2Enabled inPUSCH-ServingCellConfig is configured for the cell and set to ‘enable’.If the PUSCH indicated by the DCI is overlapping with one or more PUCCHchannels, then the transport block is multiplexed, otherwise thetransport block is transmitted on the PUSCH indicated by the DCI. Ifuplink switching gap is triggered, T_switch equals to the switching gapduration and for the UE configured with RRC parameteruplinkTxSwitchingOption set to ‘dualUL’ for uplink carrier aggregationμUL=min(μUL,carrier1, μUL,carrier2), otherwise T_switch=0. For PUSCHpreparation time for PUSCH timing capability 1, PUSCH preparation timeN2 is 10, 12, 23 and 36 symbols for μ=0, 1, 2 and 3, respectively. ForPUSCH preparation time for PUSCH timing capability 2, PUSCH preparationtime N2 is 5, 5.5 and 11 symbols (for frequency range (FR) 1) for μ=0, 1and 2, respectively.

The slot format based procedure is described. If a PUSCH is scheduled bya DCI or a PUSCH with configured grant is configured, the PUSCH istransmitted unless otherwise stated.

This procedure may apply for a serving cell that is included in a set ofserving cells configured to a UE by RRC parameterslotFormatCombToAddModList and slotFormatCombToReleaseList,availableRB-SetsToAddModList and availableRB-SetsToRelease,switchTriggerToAddModList and switchTriggerToReleaseList, orco-DurationsPerCellToAddModList and co-DurationsPerCellToReleaseList.

A SFI-index field value in a DCI format 2_0 may indicate to a UE a slotformat for each slot in a number of slots for each DL BWP or each UL BWPstarting from a slot where the UE detects the DCI format 2_0. The numberof slots may be equal to or larger than a PDCCH monitoring periodicityfor DCI format 2_0. The SFI-index field may include maxSFIindex bitswhere maxSFIindex is the maximum value of the values provided bycorresponding RRC parameter slotFormatCombinationId. A slot format maybe identified by a corresponding format index as provided in the tablein which each entry specifies a respective combination of ‘D’, ‘U’and/or ‘F’, where ‘D’ denotes a downlink symbol, ‘U’ denotes an uplinksymbol, and ‘F’ denotes a flexible symbol. The index 255 may indicatethat UE determines the slot format for the slot based ontdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated and,if any, on detected DCI formats.

For a set of symbols of a slot, a UE may not expect to detect a DCIformat 2_0 with an SFI-index field value indicating the set of symbolsof the slot as uplink and to detect a DCI format indicating to the UE toreceive PDSCH or CSI-RS in the set of symbols of the slot.

For a set of symbols of a slot, a UE may not expect to detect a DCIformat 2_0 with an SFI-index field value indicating the set of symbolsin the slot as downlink and to detect a DCI format, a RAR UL grant,fallbackRAR UL grant, or successRAR indicating to the UE to transmitPUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot.

For a set of symbols of a slot that are indicated as downlink/uplink bytdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, theUE may not expect to detect a DCI format 2_0 with an SFI-index fieldvalue indicating the set of symbols of the slot as uplink/downlink,respectively, or as flexible.

For a set of symbols of a slot indicated to a UE as flexible bytdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated ifprovided, or when tdd-UL-DL-ConfigurationCommon andtdd-UL-DL-ConfigurationDedicated are not provided to the UE, and if theUE detects a DCI format 2_0 providing a format for the slot using a slotformat value other than 255, at least the following A) to E) may beapplied. A) If an SFI-index field value in DCI format 2_0 indicates theset of symbols of the slot as flexible and the UE detects a DCI format,a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UEto transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of theslot the UE transmits the PUSCH, PUCCH, PRACH, or SRS in the set ofsymbols of the slot. B) If an SFI-index field value in DCI format 2_0indicates the set of symbols of the slot as flexible, and the UE doesnot detect a DCI format indicating to the UE to receive PDSCH or CSI-RS,or the UE does not detect a DCI format, a RAR UL, fallbackRAR UL grant,or successRAR grant indicating to the UE to transmit PUSCH, PUCCH,PRACH, or SRS in the set of symbols of the slot, the UE does nottransmit or receive in the set of symbols of the slot. C) If the UE isconfigured by higher layers to transmit PUCCH, or PUSCH, or PRACH in theset of symbols of the slot, the UE transmits the PUCCH, or the PUSCH, orthe PRACH in the slot only if an SFI-index field value in DCI format 2_0indicates the set of symbols of the slot as uplink. D) A UE does notexpect to detect an SFI-index field value in DCI format 2_0 indicatingthe set of symbols of the slot as downlink and also detect a DCI format,a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UEto transmit SRS, PUSCH, PUCCH, or PRACH, in one or more symbols from theset of symbols of the slot. E) A UE does not expect to detect anSFI-index field value in DCI format 2_0 indicating the set of symbols ofthe slot as downlink or flexible if the set of symbols of the slotincludes symbols corresponding to any repetition of a PUSCH transmissionactivated (i.e. scheduled) by an UL Type 2 grant PDCCH.

If a UE is configured by higher layers to transmit SRS, or PUCCH, orPUSCH, or PRACH in a set of symbols of a slot and the UE detects a DCIformat 2_0 with a slot format value other than 255 that indicates a slotformat with a subset of symbols from the set of symbols as downlink orflexible, or the UE detects a DCI format indicating to the UE to receiveCSI-RS or PDSCH in a subset of symbols from the set of symbols, then thefollowing A), B) and C) may be applied. A) If the UE does not indicatethe capability of partialCancellation, the UE does not expect to cancelthe transmission of the PUCCH or PUSCH or PRACH in the set of symbols ifthe first symbol in the set occurs within T_(proc,2) relative to a lastsymbol of a CORESET where the UE detects the DCI format; otherwise, theUE cancels the PUCCH, or the PUSCH, or an actual repetition of thePUSCH, or the PRACH transmission in the set of symbols. B) If the UEindicates the capability of partialCancellation, the UE does not expectto cancel the transmission of the PUCCH or PUSCH or PRACH in symbolsfrom the set of symbols that occur within T_(proc,2) relative to a lastsymbol of a CORESET where the UE detects the DCI format. The UE cancelsthe PUCCH, or the PUSCH, or an actual repetition of the PUSCH, or thePRACH transmission in remaining symbols from the set of symbols. C) TheUE does not expect to cancel the transmission of SRS in symbols from thesubset of symbols that occur within T_(proc,2) relative to a last symbolof a CORESET where the UE detects the DCI format. The UE cancels the SRStransmission in remaining symbols from the subset of symbols. T_(proc,2)is the PUSCH preparation time for the corresponding UE processingcapability assuming d_2,1=1 and p corresponds to the smallest SCSconfiguration between the SCS configuration of the PDCCH carrying theDCI format and the SCS configuration of the SRS, PUCCH, PUSCH or μ_r,where μ_r corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise μ_r=0.

If the slot-counting type configuration indicates that the number ofrepetitions to be counted based on contiguous slots, the above-describedprocessing time requirement that “UE does not expect to cancel thetransmission of the PUSCH in the set of symbols if the first symbol inthe set occurs within T_(proc,2) relative to a last symbol of a CORESETwhere the UE detects the DCI format, otherwise UE cancels the PUSCHtransmission” may be applied. If the slot-counting type configurationindicates that the number of repetitions to be counted based onavailable slots, the processing time requirement may be relaxed. Forexample, “UE does not expect to cancel the transmission of the PUSCH inthe set of symbols if the first symbol in the set occurs withinT_(proc,2)+d_x relative to a last symbol of a CORESET where the UEdetects the DCI format, otherwise UE cancels the PUSCH transmission” maybe applied, where d_x is a positive value. In other words, If the numberof repetitions for PUSCH repetition Type A is counted based oncontiguous slots, the processing time requirement of T_(proc,2) may beapplied. If the number of repetitions for PUSCH repetition Type A iscounted based on available slots, the longer processing time requirementmay be applied.

A UE may assume that flexible symbols in a CORESET configured to the UEfor PDCCH monitoring are downlink symbols if the UE does not detect anSFI-index field value in DCI format 2_0 indicating the set of symbols ofthe slot as flexible or uplink and the UE does not detect a DCI formatindicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH in the setof symbols.

For a set of symbols of a slot that are indicated as flexible bytdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-ConfigurationDedicated ifprovided, or when tdd-UL-DL-ConfigurationCommon, andtdd-UL-DL-ConfigurationDedicated are not provided to the UE, and if theUE does not detect a DCI format 2_0 providing a slot format for theslot, at least the following A) may be applied. A) The UE transmitsPUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UEreceives a corresponding indication by a DCI format, a RAR UL grant,fallbackRAR UL grant, or successRAR.

If the UE is configured by higher layers to transmit SRS, or PUCCH, orPUSCH, or PRACH in the set of symbols of the slot and the UE is notprovided RRC parameter enableConfiguredUL, the following A) and B) maybe applied. A) The UE does not transmit the PUCCH, or the PUSCH, or thePRACH in the slot and does not transmit the SRS in symbols from the setof symbols in the slot, if any, starting from a symbol that is afterPUSCH preparation time T_(proc,2) for the corresponding PUSCH timingcapability assuming d_2,1=1 after a last symbol of a CORESET where theUE is configured to monitor PDCCH for DCI format 2_0 and μ correspondsto the smallest SCS configuration between the SCS configuration of thePDCCH carrying the DCI format 2_0 and the SCS configuration of the SRS,PUCCH, PUSCH or μ_r, where μ_r corresponds to the SCS configuration ofthe PRACH if it is 15 kHz or higher; otherwise μ_r=0. B) The UE does notexpect to cancel the transmission of the SRS, or the PUCCH, or thePUSCH, or the PRACH in symbols from the set of symbols in the slot, ifany, starting before a symbol that is after the PUSCH preparation timeT_(proc,2) for the corresponding PUSCH timing capability assumingd_2,1=1 after a last symbol of a CORESET where the UE is configured tomonitor PDCCH for DCI format 2_0 and μ corresponds to the smallest SCSconfiguration between the SCS configuration of the PDCCH carrying theDCI format 2_0 and the SCS configuration of the SRS, PUCCH, PUSCH orμ_r, where μ_r corresponds to the SCS configuration of the PRACH if itis 15 kHz or higher; otherwise μ_r=0.

If the slot-counting type configuration indicates that the number ofrepetitions to be counted based on contiguous slots, the above-describedprocessing time requirement that “UE does not expect to cancel thetransmission of the PUSCH in the set of symbols if the first symbol inthe set occurs within T_(proc,2) relative to a last symbol of a CORESETwhere the UE monitor the DCI format 2_0, otherwise UE cancels the PUSCHtransmission” may be applied. If the slot-counting type configurationindicates that the number of repetitions to be counted based onavailable slots, the processing time requirement may be relaxed. Forexample, “UE does not expect to cancel the transmission of the PUSCH inthe set of symbols if the first symbol in the set occurs withinT_(proc,2)+d_x relative to a last symbol of a CORESET where the UEmonitors the DCI format 2_0, otherwise UE cancels the PUSCHtransmission” may be applied, where d_x is a positive value. In otherwords, If the number of repetitions for PUSCH repetition Type A iscounted based on contiguous slots, the processing time requirement ofT_(proc,2) may be applied. If the number of repetitions for PUSCHrepetition Type A is counted based on available slots, the longerprocessing time requirement may be applied.

If the UE is configured by higher layers to transmit SRS, or PUCCH, orPUSCH, or PRACH in the set of symbols of the slot and the UE is providedenableConfiguredUL, the UE can transmit the SRS, or PUCCH, or PUSCH, orPRACH, respectively.

If a PUSCH (or a repetition of a PUSCH) in a slot is determined to betransmitted, the slot may be considered as available for the PUSCHtransmission. If a PUSCH (or a repetition of a PUSCH) in a slot isdetermined to be cancelled or not to be transmitted, of if at least onesymbol for the PUSCH in the slot is determined as a downlink symbol, theslot may be considered as not available for the PUSCH transmission.

The cancellation indication based procedure is described. If a PUSCH isscheduled by a DCI or a PUSCH with configured grant is configured, thePUSCH is transmitted unless otherwise stated.

If a UE is provided RRC parameter UplinkCancellation, the UE may beprovided, in one or more serving cells, a search space set formonitoring the first PDCCH candidate with a CCE aggregation level ofL_CI CCEs of the search space set for detection of a DCI format 2_4 witha CI-RNTI provided by ci-RNTI.

For a serving cell having an associated field in a DCI format 2_4, thefield may be denoted by N_“CI” a number of bits provided by RRCparameter ci-PayloadSize, B_“CI” a number of PRBs provided by RRCparameter frequencyRegionforCI in RRC parameter timeFrequencyRegion,T_“CI” a number of symbols, excluding symbols for reception of SS/PBCHblocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, from anumber of symbols that is provided by RRC parameter timeDurationforCI inRRC parameter timeFrequencyRegion, if the PDCCH monitoring periodicityfor the search space set with the DCI format 2_4 is one slot and thereare more than one PDCCH monitoring occasions in a slot, or is equal tothe PDCCH monitoring periodicity, otherwise, and G_“CI” a number ofpartitions for the T_“CI” symbols provided by RRC parametertimeGranularityforCI in RRC parameter timeFrequencyRegion.

An indication by a DCI format 2_4 for a serving cell may be applicableto a PUSCH transmission or an SRS transmission on the serving cell. Ifthe PUSCH transmission or the SRS transmission is scheduled by a DCIformat, the indication by the DCI format 2_4 may be applicable to thePUSCH transmission or SRS transmission only if the last symbol of thePDCCH reception providing the DCI format is earlier than the firstsymbol of the PDCCH reception providing the DCI format 2_4. For theserving cell, the UE may determine the first symbol of the T_CI symbolsto be the first symbol that is after T′_(proc,2) from the end of a PDCCHreception where the UE detects the DCI format 2_4, where T′_(proc,2) isobtained from T_(proc,2) for PUSCH processing capability 2 assumingd_2,1=d_offset·2{circumflex over ( )}(−μ_UL)·2{circumflex over ( )}(−μ)where d_offset is provided by RRC parameter delta_Offset, μ being thesmallest SCS configuration between the SCS configuration of the PDCCHand the smallest SCS configuration μ_UL provided in RRC parameterscs-SpecificCarrierList of FrequencyInfoUL or FrequencyInfoUL-SIB. TheUE may not expect to cancel the PUSCH transmission or the SRStransmission before a corresponding symbol that is T_(proc,2) assumingthat d_2,1=0 after a last symbol of a CORESET where the UE detects theDCI format 2_4.

If the slot-counting type configuration indicates that the number ofrepetitions to be counted based on contiguous slots, the above-describedprocessing time requirement that “UE does not expect to cancel thetransmission of the PUSCH in the set of symbols if the first symbol inthe set occurs within T′_(proc,2) relative to a last symbol of a PDCCHwhere the UE detects the DCI format 2_4, otherwise UE cancels the PUSCHtransmission” may be applied. If the slot-counting type configurationindicates that the number of repetitions to be counted based onavailable slots, the processing time requirement may be relaxed. Forexample, “UE does not expect to cancel the transmission of the PUSCH inthe set of symbols if the first symbol in the set occurs withinT′_(proc,2)+d_x relative to a last symbol of a PDCCH where the UEdetects the DCI format 2_4, otherwise UE cancels the PUSCH transmission”may be applied, where d_x is a positive value. In other words, If thenumber of repetitions for PUSCH repetition Type A is counted based oncontiguous slots, the processing time requirement of T′_(proc,2) may beapplied. If the number of repetitions for PUSCH repetition Type A iscounted based on available slots, the longer processing time requirementmay be applied.

A UE that detects a DCI format 2_4 for a serving cell may cancel a PUSCHtransmission (including PUSCH transmission with repetition Type A), oran actual repetition of a PUSCH transmission if the PUSCH transmissionis with repetition Type B, or an SRS transmission on the serving cellif, respectively, the transmission is PUSCH with priority 0 if the UE isprovided RRC parameter uplinkCancellationPriority, a group of symbols,from the T_“CI” symbols, has at least one bit value of ‘1’ in thecorresponding set of N_BI bits in the DCI format 2_4 and includes asymbol of the (repetition of the) PUSCH transmission or of the SRStransmission, and a group of PRBs, from the B_“CI” PRBs, has acorresponding bit value of ‘1’ in the set of bits corresponding to thegroup of symbols in the DCI format 2_4 and includes a PRB of the(repetition of the) PUSCH transmission or of the SRS transmission. Thecancellation of the (repetition of the) PUSCH transmission may includeall symbols from the earliest symbol of the (repetition of the) PUSCHtransmission that is in a group of symbols having corresponding bitvalues of ‘1’ in the DCI format 2_4. The cancellation of the SRStransmission may include only symbols that are in one or more groups ofsymbols having corresponding bit values of ‘1’ in the DCI format 2_4

If, based on an indication by a DCI format 2_4, a UE cancels a PUSCHtransmission or an SRS transmission, the UE may not expect to bescheduled by a second DCI format to transmit a PUSCH or an SRS oversymbols that include symbols of the cancelled PUSCH transmission or SRStransmission, where the last symbol of the PDCCH reception providing thesecond DCI format is later than the first symbol of the PDCCH receptionproviding the DCI format 2_4.

If a PUSCH (or a repetition of a PUSCH) in a slot is determined to betransmitted, the slot may be considered as available for the PUSCHtransmission. If a PUSCH (or a repetition of a PUSCH) in a slot isdetermined to be cancelled or not to be transmitted, the slot may beconsidered as not available for the PUSCH transmission.

When the number of repetitions is counted based on available slots,there may be several sub-options in terms of consideration of theconditions in PUSCH-priority based procedure, slot configuration basedprocedure, slot format based procedure and cancellation indication basedprocedure. The conditions according to the slot configuration proceduremay be always applicable. Whether the conditions in the other proceduresare applicable may be depending on a certain RRC configuration.

The first sub-option is to have a single slot-counting typeconfiguration which is applicable to all the conditions. Morespecifically, if the slot-counting type configuration indicates that thenumber of repetitions to be counted based on available slots, and if anavailable-slot type configuration (the RRC configuration or RRCparameter which indicates whether the available slots are determinedbased on only semi-static configuration or based on both semi-staticconfiguration and dynamic signaling, this configuration may or may notbe the same as the slot-counting type configuration) indicates thatdynamic signaling is used for the determination of the available slots,the available slots may be determined according to all the conditions ofwhich corresponding RRC configurations are provided. For example, theconditions in PUSCH-priority based procedure may be applicable ifphy-PriorityIndex or priorityIndicatorDCI is provided, while theconditions in PUSCH-priority based procedure may be not applicable ifphy-PriorityIndex or priorityIndicatorDCI (the procedure whichdetermines whether PUSCH is transmitted or not based on the priorityindex of the PUSCH)) is not provided. The conditions in slot formatbased procedure may be applicable if SlotFormatCombinationsPerCell (i.e.RRC parameter/configuration which causes the slot format based procedure(the procedure which determines whether PUSCH is transmitted or notbased on the slot format)) is provided, while the conditions in slotformat based procedure may be not applicable ifSlotFormatCombinationsPerCell is not provided. The conditions incancellation indication based procedure may be applicable ifUplinkCancellation (i.e. RRC parameter/configuration which causes thecancellation indicator based procedure (the procedure which determineswhether PUSCH is transmitted or not based on the cancellationindicator)) is provided, while the conditions in cancellation indicationbased procedure may be not applicable if UplinkCancellation is notprovided.

With the first sub-option, if the UE is capable of a certain coverageenhancement feature(s) and/or if the UE is provided with a certaincoverage enhancement configuration(s), alternatively or additionally ifthe UE is provided with a slot-counting type configuration whichindicates the PUSCH repetition to be counted based on available slotsand/or if the UE is provided with an available-slot type configurationwhich indicates dynamic signaling to be used for the determination ofthe available slots, the following may be applied. For both Type 1 andType 2 PUSCH transmissions with a configured grant, when K>1, the UE mayrepeat the TB across the K available slots (i.e. the first K slots whichare available for the PUSCH transmission) applying the same symbolallocation in each slot. The K available slots may be determinedaccording to the conditions in the slot configuration based procedureand additionally in the PUSCH-priority based procedure, the slot formatbased procedure and the cancellation indication based procedure.

With the first sub-option, if the UE is capable of a certain coverageenhancement feature(s) and/or if the UE is provided with a certaincoverage enhancement configuration(s), alternatively or additionally ifthe UE is provided with a slot-counting type configuration whichindicates the PUSCH repetition to be counted based on available slotsand/or if the UE is provided with an available-slot type configurationwhich indicates only semi-static configuration to be used for thedetermination of the available slots, the following may be applied. Forboth Type 1 and Type 2 PUSCH transmissions with a configured grant, whenK>1, the UE may repeat the TB across the K available slots (i.e. thefirst K slots which are available for the PUSCH transmission) applyingthe same symbol allocation in each slot. The K available slots may bedetermined according to the conditions in the slot configuration basedprocedure but without referring to the conditions in the PUSCH-prioritybased procedure, the slot format based procedure and the cancellationindication based procedure.

The second sub-option is to have several slot-counting typeconfiguration, each is applicable to the conditions in a respectiveprocedure. More specifically, if the available-slot type configurationfor PUSCH-priority based procedure indicates that PUSCH-priority basedtransmissions/cancellations are used for the determination of theavailable slots, the available slots may be determined according to thePUSCH-priority based procedure. Similarly, if the available-slot typeconfiguration for slot format based procedure indicates that slot formatbased transmissions/cancellations are used for the determination of theavailable slots, the available slots may be determined according to theslot format based procedure. If the available-slot type configurationfor cancellation indication based procedure indicates that cancellationindication based transmissions/cancellations are used for thedetermination of the available slots, the available slots may bedetermined according to the cancellation indication based procedure. Forexample, the conditions in PUSCH-priority based procedure may beapplicable if phy-PriorityIndex or priorityIndicatorDCI is provided andalso if the available-slot type configuration for PUSCH-priority basedprocedure indicating use of PUSCH-priority based procedure is provided,while the conditions in PUSCH-priority based procedure may be notapplicable otherwise. The conditions in slot format based procedure maybe applicable if SlotFormatCombinationsPerCell is provided and also ifthe available-slot type configuration for slot format based procedureindicating use of slot format based procedure is provided, while theconditions in slot format based procedure may be not applicableotherwise. The conditions in cancellation indication based procedure maybe applicable if UplinkCancellation is provided and also if theavailable-slot type configuration for cancellation indication basedprocedure indicating use of cancellation indication based procedure isprovided, while the conditions in cancellation indication basedprocedure may be not applicable otherwise. Any combination of the abovemay also apply. For example, if the available-slot type configurationfor PUSCH-priority based procedure is provided, and if theavailable-slot type configuration for slot format based procedure isprovided, but if the available-slot type configuration for cancellationindication based procedure is not provided, the available slot may bedetermined based on the conditions in slot configuration basedprocedures and also the conditions in PUSCH-priority based procedure andslot format based procedure, but the conditions according tocancellation indication based procedure are not referred to for thedetermination of available slots.

With the second sub-option, if the UE is capable of a certain coverageenhancement feature(s) and/or if the UE is provided with a certaincoverage enhancement configuration(s), alternatively or additionally ifthe UE is provided with a slot-counting type configuration whichindicates the PUSCH repetition to be counted based on available slotsand if the UE is provided with at least one of available-slot typeconfigurations for PUSCH-priority based procedure, slot format basedprocedure and cancellation indication based procedure, the following maybe applied. For both Type 1 and Type 2 PUSCH transmissions with aconfigured grant, when K>1, the UE may repeat the TB across the Kavailable slots (i.e. the first K slots which are available for thePUSCH transmission) applying the same symbol allocation in each slot.The K available slots may be determined according to the conditions inthe slot configuration based procedure and additionally in thePUSCH-priority based procedure, the slot format based procedure and thecancellation indication based procedure if, respectively, theavailable-slot type configuration for PUSCH-priority based procedure,the available-slot type configuration for slot format based procedure,or the available-slot type configuration for cancellation indicationbased procedure is provided.

If only semi-static configuration is used for the determination of theavailable slots and/or any dynamic signaling is not used for thedetermination of the available slots, the UE determines the K slots fora PUSCH transmission starting from a slot indicated to the UE for thePUSCH transmission and having A) an UL symbol, as described in the slotconfiguration procedure, or flexible symbol that is not SS/PBCH blocksymbol, and B) consecutive UL symbols, as described in the slotconfiguration procedure, or flexible symbols that are not SS/PBCH blocksymbols, starting from the first symbol, equal to or larger than thenumber of symbols where the first symbol within a slot and the number ofsymbols within the slot may be provided by time domain resourceallocation information for the PUSCH.

It is noted that the aforementioned available-slot type configurationmay be referred to as a different name. The existence of theavailable-slot type configuration in RRC configuration message may meanthat the conditions in both the slot configuration procedure and theother procedure(s) are used for the determination of the available slotswhile the absence of the available-slot type configuration in RRCconfiguration message may mean that the conditions in the slotconfiguration procedure but not in the other procedure(s) are used forthe determination of the available slots. Additionally and/oralternatively, the available-slot type configuration set to the firstvalue (e.g. ‘semi-static’) may mean that the conditions in the slotconfiguration procedure but not in the other procedure(s) are used forthe determination of the available slots while the available-slot typeconfiguration set to the second value (e.g. ‘dynamic’) may mean that theconditions in both the slot configuration procedure and the otherprocedure(s) are used for the determination of the available slots.

FIG. 9 is an example configuration of a frame structure according to anaspect of the present embodiment. In FIG. 9 , a horizontal axisindicates time domain. In the time domain, slots are numbered from slot#n (slot with index n) in ascending order. Each line in the time domainindicates a slot boundary. 9001 indicates a downlink region. 9002indicates a flexible region. 9003 indicates an uplink region.

Region indicated by 9000 includes a set of region 9001, 9002 and 9003.Region 9000 may be configured based on a slot configuration. Forexample, a slot configuration may include at least a downlink region, aflexible region and an uplink region. For example, a slot configurationmay be configured such that the slot configuration starts at oneUL-to-DL switching point. Further, the slot configuration may beconfigured such that the slot configuration ends at another UL-to-DLswitching point. For example, a UL-to-DL switching point may be a pointwhere a uplink region ends and a downlink region starts.

For example, a slot configuration may be repeated in the time domain. InFIG. 9 , a slot configuration comprising 3 downlink slots, one specialslot and 1 uplink slot is repeated. Region 9000 is an instance of theslot configuration starting at slot #n and an Region 9010 is an instanceof the slot configuration starting at slot #n+5. In FIG. 9 , repetitioncycle of the slot configuration is 5 slots.

9011 indicates a downlink region. Further, 9012 indicates a flexibleregion. Further, 9013 indicates an uplink region.

For example, a slot configuration may be represented by a combination of‘D’, ‘U’ and ‘S’. ‘D’ indicates that a slot is a downlink slot. Adownlink slot is a slot with downlink region. In FIG. 9 , slot #n, slot#n+1, slot #n+2, slot #n+5, slot #n+6 and slot #n+7 are downlink slots.

‘U’ indicates that a slot is an uplink slot. An uplink slot is a slotwith uplink region. In FIG. 9 , slot #n+4 and slot #n+9 are uplinkslots.

‘S’ indicates that a slot is a special slot. A special slot is a slotwith at least two or more of a downlink regions, a flexible region andan uplink region. In FIG. 9 , slot #n+3 and slot #n+8 are special slots.

In FIG. 9 , the slot configuration may be also referred to as “DDDSU”.“DDDSU” means that the slot configuration comprises 3 downlink slots, 1special slot and 1 uplink slot.

A configuration of special slot may be represented by “XDYFZU”. Here, Xis the number of downlink symbols, Y is the number of flexible symbolsand Z is the number of uplink symbols. For example, “10D2F2U” indicatesthat a special slot comprises 10 downlink symbols, 2 flexible symbolsand 2 uplink symbols.

A downlink symbol is an OFDM symbol in a downlink region. A flexiblesymbol is an OFDM symbol in a flexible region. An uplink symbol is anOFDM symbol in an uplink region.

A slot configuration may be provided by RRC parameters. For example, aslot configuration may be configured by a common parameter included insystem information such as SIB1. The common parameter may be alsoreferred to as tdd-UL-DL-ConfigurationCommon.

For example, terminal device 1 may determine a referencesubcarrier-spacing configuration u_(ref) and a first TDD pattern fromthe common parameter. The first TDD pattern includes one or more of T1to T5. T1 is a configuration period P in milliseconds provided byreferenceSubcarrierSpacing. T2 is the number d_(slots) of slotsindicating consecutive downlink slots provided by nrofDownlinkSlots. T3is the number d_(sym) of consecutive downlink symbols provided bynrofDownlinkSymbols. T4 is the number u_(slots) of consecutive uplinkslots provided by nrofUplinkSlots. T5 is the number u_(sym) ofconsecutive uplink symbols provided by nrofUplinkSymbols.

FIG. 10 is an example configuration of a slot configuration according toan aspect of the present embodiment. In FIG. 10 , a horizontal axisindicates time domain. In the time domain, slots are numbered from slot#n (slot with index n) in ascending order. Each line in the time domainindicates a slot boundary. 10000 indicates a slot configuration. In theslot configuration, first d_(slots)=2 slots as indicated by Region 10001are configured as downlink slots. In the slot configuration, lastu_(slots)=1 slot as indicated by Region 10002 is configured as an uplinkslot. In the slot configuration, first d_(sym) OFDM symbols starting atfirst OFDM symbol in a slot with index n+d_(slots) as indicated byRegion 10003 is configured as downlink symbols. In the slotconfiguration, last u_(sym) OFDM symbols before first OFDM symbol in aslot with index n+S−u_(slots) as indicated by Region 10004 is configuredas uplink symbols. In the slot configuration, the remaining OFDM symbolsnot indicated as either downlink region or uplink region as indicated byRegion 1005 are flexible symbols.

A slot configuration may be modified by a UE-specific parameter. TheUE-specific parameter may be also referred to astdd-UL-DL-ConfigurationDedicated.

If the UE-specific parameter is provided to terminal device 1, theUE-specific parameter may modify (or reconfigure) the slot configurationprovided by the common parameter. For example, the UE-specific parametermay modify (or reconfigure) flexible region in the slot configuration.

For example, terminal device 1 may determine a list including a set ofslot reconfigurations by the UE-specific parameter. In each slotreconfiguration in the set, at least one or both of an index of a slotand an indication of TDD pattern of the slot may be provided. Theindication may indicate one out of ‘all DL’, ‘all UL’ and ‘explicit’. Ina case that ‘all DL’ is indicated for the slot, the slot configurationin the slot is reconfigured as downlink region. In a case that ‘all UL’is indicated for the slot, the slot configuration in the slot isreconfigured as uplink region. In a case that ‘explicit’ is indicatedfor the slot, the slot configuration in the slot is reconfigured byexplicit indication corresponding to ‘explicit’. Indication ‘explicit’corresponds to information indicating a TDD pattern in a slot. Theinformation includes information indicating the number of downlinksymbols starting at the beginning of the slot and information indicatingthe number of uplink symbols ending at the end of the slot. Theremaining OFDM symbols between downlink symbols and uplink symbols areflexible symbols.

Terminal device 1 may receive a physical signal if terminal device 1 isconfigured by a higher layer or indicated by a DCI format to receive thephysical signal in the downlink region.

Terminal device 1 may transmit a physical signal if terminal device 1 isconfigured by a higher layer or indicated by a DCI format to transmitthe physical signal in the uplink region.

In a case that monitoring of DCI format 2_0 is not configured by ahigher layer, terminal device 1 may receive a physical signal ifterminal device 1 is indicated by a DCI format scheduling the physicalchannel to receive in the downlink region or the flexible region.

In a case that monitoring of DCI format 2_0 is not configured by ahigher layer, terminal device 1 may transmit a physical signal ifterminal device 1 is indicated by a DCI format scheduling the physicalsignal to transmit in the uplink region or the flexible region.

In a case that monitoring of DCI format 2_0 is configured by a higherlayer, terminal device 1 may determine whether to receive a physicalsignal or not at least based on indication in the DCI format 2_0.

In a case that monitoring of DCI format 2_0 is configured by a higherlayer, terminal device 1 may determine whether to transmit a physicalsignal or not at least based on indication in the DCI format 2_0.

Configuration regarding monitoring of DCI format 2_0 may include atleast one or more of S1 to S3. S1 is an identifier of a serving cell. S2is information indicating bit location of field for index of a slotformat indicator. S3 is a set of slot format combinations. Here, eachslot format combination may include one or more slot formats. Each ofslot format combination may include an index of a slot format indicator.Each slot format may indicate a TDD pattern within a slot. For example,slot format #0 indicates that all OFDM symbols in a slot are downlinksymbol. For example, slot format #1 indicates that all OFDM symbols in aslot are uplink symbol. For example, one slot format indicates thatfirst 9 OFDM symbols in a slot are downlink symbol, next 3 OFDM symbolsin the slot are flexible symbol and remaining 2 OFDM symbols are uplinksymbol. For example, one slot format indicates that terminal device 1interpret as if monitoring of DCI format 2_0 is not configured. OtherTDD patterns in a slot are not precluded.

In a case that terminal device 1 detects a DCI format 2_0 in a firstslot, terminal device 1 applies a slot format combination indicatedthrough an index of slot format indicator in the DCI format 2_0. Forexample, the slot format combination may be applied to slots starting atthe first slot.

At least based on an indication in DCI format 2_0, behavior of PUSCHtransmission may be controlled. For example, a PUSCH transmission may berepetition of a PUSCH instance where the PUSCH instance is definedwithin a slot.

A PUSCH instance may be a unit of baseband signal generation. Here, thebaseband signal generation may be performed by the baseband unit 13.

FIG. 11 is an example configuration of the baseband unit 13 in thewireless transmission unit 10 a according to an aspect of the presentembodiment. The baseband unit 13 may include at least a part or all ofEncoder 12000, Scrambler 11001, Modulator 11002, Layer mapper 11003,Transform precoder 11004, Precoder 11005, Resource element mapper 11006and Time-continuous signal generator 11007.

A transport block may be provided to Encoder 12000 from a higher layer.For example, a transport block may be provided to Encoder 12000 throughUL-SCH from MAC layer processing unit 15. Encoder 12000 processes thetransport block into a sequence b of coded bits. The sequence of thecoded bits may be provided to Scrambler 11001. An element in position kof the sequence b may be referred to as b(k). The position k is in therange from 0 to M_(bit)−1. The position k is represented by an integernumber. The M_(bit) represents the length of the sequence b.

For example, Scrambler 11001 may scramble the sequence b of the codedbits by using a pseudo-random code c. For example, the element b(k) maybe scrambled by an element c(k) in position k of the pseudo-random codec. For example, Scrambler 11001 may output a sequence b^(a) bycalculating b(k)=mod(b(k)+c(k), 2). The b^(a)(k) is an element inposition k of the sequence b^(a). In a case that the baseband unit 13doesn't include Scrambler 11001, the sequence b of the coded bits may beinput to the b_(a).

The pseudo-random code c may be a sequence of bits generated byScrambler 11001. For example, the pseudo-random code c may be generatedby an equation with initialization variable. The initialization variablemay determine or control an output from the equation. The initializationvariable may be determined at least based on RNTI used for scheduling anuplink transmission conveying the transport block.

For example, Modulator 11002 may perform a modulation to the sequenceb_(a) and generate a sequence d of complex-valued symbols. An element inposition j of the sequence d is referred to as d(j). The position j isin the range from 0 to M_(symb)−1. The position j is represented by aninteger number. The M_(symb) represents the length of the sequence d. Ina case that the baseband unit 13 doesn't include Modulator 12002, thesequence b^(a) of the coded bits may be input to the d.

For example, the modulation may be 2/pi BPSK (Binary Phase ShiftKeying), QPSK (Quadrature Phase Shift Keying), 16QAM (QuadratureAmplitude Modulation), 64QAM or 256QAM.

For example, Layer mapper 11003 may perform layer mapping to thesequence d. After layer mapping, N_(v) sequences each with lengthM^(layer) _(symb) are generated. The N_(v) is the number of layers forthe PUSCH. The v^(th) sequence in the N_(v) sequences is referred to asx^((v)). An element in position h of the sequence x^((v)) is referred toas x^((v))(h). The position h is in the range from 0 to M^(layer)_(symb-1). The position h is represented by an integer number. In a casethat the number N, is 1, Layer mapper 11003 may not perform layermapping. In a case that the layer mapping is not performed to thesequence d, the sequence d may be input to x⁽⁰⁾.

For example, Transform precoder 11004 may perform a transform precodingto the sequence x^((v)) and generate a sequence y^((v)). In a case thatthe transform precoding is not performed to the sequence x^((v)), thesequence x^((v)) may be input to the sequence y^((v)).

For example, Precoder 11005 may perform a precoding to the sequencey^((v)) After the precoding, N_(p) sequences each with length M^(layer)_(symb) are generated. The N_(p) is the number of antenna ports for thePUSCH. The p^(th) sequence in the N_(p) sequences is referred to asz^((p)). An element in position h of the sequence z^((p)) is referred toas z^((p))(h). In a case that the number N_(p) is 1, Precoder 11005 maynot perform the precoding. In a case that the precoding is not performedto the sequence y^((v)), the sequence y^((v)) may be input to z^((p)).

For example, Resource element mapper 11006 may perform a RE mapping. Ina RE mapping, a group of elements z(h)=[z⁽⁰⁾(h), . . . , z^((Np-1))(h)]is mapped to a resource element.

For example, Time-continuous signal generator 11007 may perform atime-continuous signal generation based on contents in the resourceelements. The contents in the resource elements are determined based onthe RE mapping. The time-continuous signal generated by Time-continuoussignal generator 11007 is provided to RF unit 12.

The baseband unit 33 may include corresponding components for receptionof the PUSCH as the baseband unit 13.

FIG. 12 is an example configuration of Encoder 12000 according to anaspect of the present embodiment. Encoder 12000 may include at least apart or all of CRC addition unit 12001, CB segmentation unit 12002,Encoding unit 12003, Rate matching unit 12004 and Multiplexing unit12005.

For example, a transport block input to Encoder 12000 is an input to CRCaddition unit 12001. In CRC addition unit 12001, a CRC sequence is addedto the transport block. A bit sequence after CRC sequence addition isinput to Code block segmentation unit 12002. In a case that a CRCsequence is not added to the transport block, the transport block isinput to Code block segmentation unit 12002.

For example, a sequence input to Code block segmentation unit 12002 issegmented into multiple code blocks in a case that the length of thesequence is larger than a certain value. In a case that the sequence issegmented into multiple code blocks, a CRC sequence is added to eachcode block. Each code block after the CRC sequence addition is input toEncoding unit 12003. In a case that the sequence is not segmented intomultiple code blocks, a single code block is input to Encoding unit12003. In a case that the sequence is not segmented into multiple codeblocks, a CRC sequence is not added to the single code block. In a casethat the sequence is not segmented into multiple code blocks, the singlecode block without addition of a CRC sequence is input to Encoding unit12003.

For example, a code block with index r (code block #r) input to Encodingunit 12003 is encoded by LDPC coding such as QC-LDPC (Quasi-Cyclic LowDensity Parity Check) coding. The index r is in the range from 0 to C−1.The C is the number of code blocks determined in Code block segmentationunit 12002. Coded bits d^(r) for the code block #r after LDPC coding isinput to Rate matching unit 12004.

For example, Rate matching unit 12004 performs a bit-selectionprocedure. In the bit-selection procedure, the coded bits d^(r) for thecode block r is written into a circular buffer of length N_(cb).

FIG. 13 is an example of the bit-selection procedure according to anaspect of the present embodiment. In the bit-selection procedure, twovalues k and j are set to 0 as Step 0. Next, in Step 1, Rate matchingunit 12004 checks if the value k is smaller than a rate matching outputsequence length E_(r). If the value k is smaller than the rate matchingoutput sequence length E_(r), Rate matching unit 12004 goes to Step 2.If the value k is not smaller than the rate matching output sequencelength E_(r), Rate matching unit 12004 terminates the bit-selectionprocedure.

Here, the rate matching output sequence length E_(r) represents thenumber of available bits for transmission of the code block #r. Forexample, the rate matching output sequence length E_(r) for code block#r may be calculated at least based on a part or all of modulation orderQ_(m), the number N_(v) of layers for the PUSCH, the number C′ and thenumber G. For example, the rate matching output sequence length E_(r)for code block r may be calculated byE_(r)=N_(L)Q_(m)floor(G/(N_(L)Q_(m)C′)) orE_(r)=N_(L)Q_(m)ceil(G/(N_(L)Q_(m)C′)).

Here, the number C′ represents the number of code blocks. The number Grepresents the number of available bits for transmission of UL-SCH. Forexample, the number G may represent the number of available bits fortransmission of UL-SCH in the PUSCH instance.

In Step 2, Rate matching unit 12004 checks if d^(r)(mod(k₀+j, N_(cb)))is not <NULL>. If d^(r)(mod(k₀+j, N_(cb))) is not <NULL>, Rate matchingunit 12004 goes to Step 3. If d^(r)(mod(k₀+j, N_(cb))) is <NULL>, Ratematching unit 12004 goes to Step 5.

Here, “d^(r)(mod(k₀+j, N_(cb))) is <NULL>” means <NULL> is set tod^(r)(mod(k₀+j, N_(cb))). <NULL> may be set to some elements of d^(r)when an element corresponds to a filler bit for LDPC coding.

Here, an element in position k of d^(r) is referred to as d^(r)(k).

In Step 3, Rate matching unit 12004 sets a value in d^(r)(mod(k₀+j,N_(cb))) to e(k). The sequence e is a rate matching output sequence. Anelement in position k of the sequence e is referred to as e(k).

Here, k₀ represents a starting point for the circular buffer.

In Step 4, Rate matching unit 12004 increments a value k by one.

Step 5 is a sign of the end of Step 2.

In Step 6, Rate matching unit 12004 increments a value j by one.

Step 7 is a sign of the end of Step 1. Rate matching unit 12004 goesback to Step 1.

FIG. 14 is an example of a circular buffer according to an aspect of thepresent embodiment. In the circular buffer, the coded bits d^(r) aremapped clockwise starting at position indicated by RV0. Since the codedbits d_(r) includes systematic bits followed by parity bits, thesystematic bits are mapped starting at the position indicated by RV0 andthe parity bits are mapped starting at the end of the systematic bits.The region indicated by the upper right diagonal line is filled with thesystematic bits. The region indicated by the lattice line is filled withthe parity bits.

In the bit-selection procedure, bits in the circular buffer are read outstarting at the starting point k₀ with length E_(r). The bits read outfrom the circular buffer are written into the rate matching outputsequence e.

The starting point k₀ is determined based on the redundancy versionindicated or determined by a redundancy version field in an uplink DCIformat for dynamic scheduling.

For example, the starting point k₀ may be determined based on theredundancy version and an identification of an instance. For example, ina case that one DCI format schedules a repetition of a PUSCH, terminaldevice 1 may transmit multiple instances. For each instance, thestarting point k₀ may be determined. For example, in a case that 8instances (instance #0, instance #1, instance #2, instance #3, instance#4, instance #5, instance #6, instance #7) are scheduled by one DCIformat, the starting point k₀ may be determined 8 times.

For example, a sequence of RV (redundancy version) may be provided tothe terminal device 1. In a case that a sequence of RV is provided, a RVis allocated to each instance in the multiple instances based on thesequence. For example, in a case that the sequence [0, 2, 3, 1] oflength N_(s) is provided, (mod (n, N_(s))+1)^(th) value in the sequencemay be allocated to n^(th) instance. The starting point k₀ of n^(th)instance may be determined based on the allocated RV for n^(th)instance.

FIG. 15 is an example configuration of first type repetition of a PUSCHscheduled by a DCI format in multiple slots according to an aspect ofthe present embodiment. In FIG. 15, 15000 indicates a PDCCH with a DCIformat which schedules a PUSCH with a first type repetition. It isassumed that the first type repetition is scheduled in slots starting atslot #n+3 in FIG. 15 . 15001 indicates an instance of the PUSCH in slot#n+3. Here, a value S indicates a starting OFDM symbol index within theslot for the instance 15001. Also, a value L indicates a length in termsof the number of OFDM symbols for the instance 15001. 6 instancesindicated by 15002 to 15007 are followed by the instance 15001. Eachinstance is mapped within a slot. In FIG. 15 , it is assumed that thenumber K_(rep) of repetitions is 7.

A TDRA field in the DCI format may provide a value S and a value L.

In FIG. 15 , the S is applied to all the instances for the PUSCH. Forexample, all the instances apply the same starting OFDM symbol indexwithin a slot. In FIG. 15 , the L is applied to all the instances forthe PUSCH. For example, all the instances apply the same length in termsof the number of OFDM symbols.

In a first type repetition, multiple instances for a PUSCH may beallocated on K_(rep) continuous slots starting at a slot determined by aDCI format scheduling the PUSCH. For example, in a case that a DCIformat scheduling the PUSCH includes a TDRA field, the TDRA field mayprovide a value K for determining the starting slot for the PUSCH. Forexample, the value K is in unit of slots. For example, the terminaldevice 1 may determine the starting slot as slot #(n+K) in a case that aPDCCH including the DCI format is detected in slot #n. In a case thatthe DCI format doesn't include a TDRA field, the value K may be providedby a RRC layer through a RRC parameter.

A sequence of RV for the first type repetition may be provided to theterminal device 1. For example, the sequence may be provided by a RRClayer through a RRC parameter. In a case that a sequence of RV isprovided for the first type repetition, (mod (n, N_(s))+1)^(th) value inthe sequence may be allocated to n^(th) instance. Here, an index may beprovided to each instance for the PUSCH in ascending order in the timedomain.

For a first type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot configuration, transmission of theinstance may be omitted (or dropped, cancelled, not transmitted).

For a first type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot format, transmission of theinstance may be omitted.

For a first type repetition, in a case that an instance overlaps withanother uplink signal with a higher priority than the priority for thePUSCH, transmission of the instance may be omitted. For example, theuplink signal may be a second PUSCH with higher priority than thepriority of the PUSCH. For example, the priority for a PUSCH may beprovided by a DCI format scheduling the PUSCH.

FIG. 16 is an example configuration of second type repetition of a PUSCHscheduled by a DCI format in multiple slots according to an aspect ofthe present embodiment. In FIG. 16, 16000 indicates a PDCCH with a DCIformat which schedules a PUSCH with a second type repetition. It isassumed that the second type repetition is scheduled in slots startingat slot #n+3. 16001 indicates an instance of the PUSCH in slot #n+3.Here, a value S indicates a starting OFDM symbol index within the slotfor the instance. Also, a value L indicates a length in terms of thenumber of OFDM symbols for the instance. 3 instances indicated by 16002to 16004 are followed by the instance 16001. Each instance is mappedwithin a slot. In FIG. 16 , it is assumed that the number K_(rep) ofrepetitions is 4.

In FIG. 16 , S is applied to all instances for the PUSCH. For example,all instances apply the same starting OFDM symbol index within a slot.In FIG. 16 , L is applied to all instances for the PUSCH. For example,all instances apply the same length in terms of the number of OFDMsymbols.

In a second type repetition, the multiple instances for a PUSCH may beallocated on K_(rep) continuous available slots starting at a slotdetermined by a DCI format scheduling the PUSCH. For example, in a casethat a DCI format scheduling the PUSCH includes a TDRA field, the TDRAfield may provide a value K for determining the starting slot for thePUSCH. For example, the value K is in unit of slots. For example, in acase that the terminal device 1 may determine the starting slot as slot#(n+K). In a case that the DCI format doesn't include a TDRA field, thevalue K may be provided by a RRC layer through a RRC parameter.

In a second type repetition, K_(rep) continuous available slots may bedetermined by a slot configuration. For example, a slot may be availablein a case that a set of OFDM symbols allocated for an instance in theslot doesn't overlap with any downlink symbol which is determined by aslot configuration. For example, a slot may be available in a case thata set of OFDM symbols determined by a value S and a value L in the slotdoesn't overlap with any downlink symbol which is determined by a slotconfiguration. The value S and the value L may be provided by the TDRAfield in the DCI format. In FIG. 16 , slot #n+3 is available for asecond type repetition since the set of OFDM symbols allocated for theinstance 16001 doesn't overlap with 9001. In other words, slot #n+3 isavailable for a second type repetition since each OFDM symbol allocatedfor the instance 16001 overlaps with 9002 or 9003. In FIG. 16 , slot#n+4 is available for a second type repetition since the set of OFDMsymbols allocated for the instance 16002 doesn't overlap with 9001. Inother words, slot #n+4 is available for a second type repetition sinceeach OFDM symbols allocated for the instance 16002 overlaps with 9003.In FIG. 16 , slot #n+5 is not available for a second type repetitionsince the set of OFDM symbols determined by the value S and the value Loverlaps with 9011. In other words, slot #n+5 is not available for asecond type repetition since some OFDM symbols determined by the value Sand the value L doesn't overlap with 9002 or 9003.

A sequence of RV may be provided for the second type repetition to theterminal device 1. For example, the sequence may be provided by a RRClayer through a RRC parameter. In a case that a sequence of RV isprovided for the second type repetition, (mod (n, N_(s))+1)^(th) valuein the sequence may be allocated to n^(th) instance. Here, an index maybe provided to each instance for the PUSCH in ascending order in thetime domain.

For example, a first sequence of RV and a second sequence of RV may beprovided to the terminal device 1. For example, the first sequence maybe used for a first type repetition. For example, the second sequencemay be used for a second type repetition.

For example, the first sequence may be provided by a RRC layer through afirst RRC parameter. For example, the second sequence may be provided bya RRC layer through a second RRC parameter which is different from thefirst RRC parameter.

For a second type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot configuration, transmission of theinstance may be omitted. On the other hand, for a second typerepetition, there may be no case that an instance overlaps with adownlink symbol determined by a slot configuration since the collisionhandling with the downlink symbol by the slot configuration may havebeen done already in a procedure of determining the K_(rep) continuousavailable slots. Therefore, for a second type repetition, transmissionof the instance may not be omitted based on the slot configuration. Forexample, for a second type repetition, the terminal device 1 may notdetermine, based on the slot configuration, whether an instance isomitted or not. For example, the terminal device 1 may not perform aprocess of determining, based on the slot configuration, whether aninstance is omitted or not.

For a second type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot format, transmission of theinstance may be omitted.

For a second type repetition, in a case that an instance overlaps withanother uplink signal with a higher priority than the priority for thePUSCH, transmission of the instance may be omitted. For example, theuplink signal may be a second PUSCH with higher priority than thepriority of the PUSCH. For example, the priority for a PUSCH may beprovided by a DCI format scheduling the PUSCH.

A third type repetition is described with FIG. 16 assuming K_(rep)=3.

In a third type repetition, multiple instances for a PUSCH may beallocated on continuous available slots starting at a slot determined bya DCI format scheduling the PUSCH.

In a third type repetition, the continuous available slots may bedetermined by a slot configuration. For example, a slot may be availablein a case that a set of OFDM symbols allocated for an instance in theslot doesn't overlap with any downlink symbol which is determined by aslot configuration. For example, a slot may be available in a case thata set of OFDM symbols determined by a value S and a value L provided bythe TDRA field in the DCI format in the slot doesn't overlap with anydownlink symbol which is determined by a slot configuration. In FIG. 16, slot #n+3 is available for a third type repetition since the set ofOFDM symbols allocated for the instance 16001 doesn't overlap with 9001.In other words, slot #n+3 is available for a third type repetition sinceeach OFDM symbol allocated for the instance 16001 overlaps with 9002 or9003. In FIG. 16 , slot #n+4 is available for a third type repetitionsince the set of OFDM symbols allocated for the instance 16002 doesn'toverlap with 9001. In other words, slot #n+4 is available for a thirdtype repetition since each OFDM symbol allocated for the instance 16002overlaps with 9003. In FIG. 16 , slot #n+5 is not available for a thirdtype repetition since the set of OFDM symbols determined by the value Sand the value L overlaps with 9011. In other words, slot #n+5 is notavailable for a third type repetition since some OFDM symbols determinedby the value S and the value L doesn't overlap with 9002 or 9003.

A sequence of RV may be provided for the third type repetition to theterminal device 1. For example, the sequence may be provided by a RRClayer through a RRC parameter. In a case that a sequence of RV isprovided for the third type repetition, (mod (n, N_(s))+1)^(th) value inthe sequence may be allocated to n^(th) instance. For example, a firstsequence of RV and a third sequence of RV may be provided to theterminal device 1. For example, the first sequence may be used for afirst type repetition. For example, the third sequence may be used for athird type repetition.

For example, the first sequence may be provided by a RRC layer through afirst RRC parameter. For example, the third sequence may be provided bya RRC layer through a third RRC parameter which is different from thefirst RRC parameter.

For a third type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot configuration, transmission of theinstance may be omitted. On the other hand, for a third type repetition,there may be no case that an instance overlaps with a downlink symboldetermined by a slot configuration since the collision handling with thedownlink symbol by the slot configuration may have been done already ina procedure of determining the continuous available slots. Therefore,for a third type repetition, transmission of the instance may not beomitted based on the slot configuration. For example, for a third typerepetition, the terminal device 1 may not determine, based on the slotconfiguration, whether an instance is omitted or not. For example, theterminal device 1 may not perform a process of determining, based on theslot configuration, whether an instance is omitted or not.

For a third type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot format, transmission of theinstance may be omitted.

For a third type repetition, in a case that an instance overlaps withanother uplink signal with a higher priority than the priority for thePUSCH, transmission of the instance may be omitted. For example, theuplink signal may be a second PUSCH with higher priority than thepriority of the PUSCH. For example, the priority for a PUSCH may beprovided by a DCI format scheduling the PUSCH.

For a third type repetition, first Kr instances are determined for thePUSCH transmission. For example, in a case that no instances areomitted, the terminal device may determine that the instance 16001,16002, and 16003 as the first K_(rep) instances. For example, in a casethat the instance 16002 is omitted due to the collision with the highpriority signal, the terminal device determines that the instance 16001,16003 and 16004 as the first K, instances. For example, in a case thatthe instance 16003 is omitted due to the collision with the highpriority signal, the terminal device determines that the instance 16001,16002 and 16004 as the first K, instances.

A fourth type repetition is described with FIG. 16 assuming K_(rep)=3.

In a fourth type repetition, multiple instances for a PUSCH may beallocated on continuous available slots starting at a slot determined bya DCI format scheduling the PUSCH.

In a fourth type repetition, the continuous available slots may bedetermined by a slot configuration. For example, a slot may be availablein a case that a set of OFDM symbols allocated for an instance in theslot doesn't overlap with any downlink symbol which is determined by aslot configuration. For example, a slot may be available in a case thata set of OFDM symbols determined by a value S and a value L provided bythe TDRA field in the DCI format in the slot doesn't overlap with anydownlink symbol which is determined by a slot configuration. In FIG. 16, slot #n+3 is available for a fourth type repetition since the set ofOFDM symbols allocated for the instance 16001 doesn't overlap with 9001.In other words, slot #n+3 is available for a fourth type repetitionsince each OFDM symbol allocated for the instance 16001 overlaps with9002 or 9003. In FIG. 16 , slot #n+4 is available for a fourth typerepetition since the set of OFDM symbols allocated for the instance16002 doesn't overlap with 9001. In other words, slot #n+4 is availablefor a fourth type repetition since each OFDM symbol allocated for theinstance 16002 overlaps with 9003. In FIG. 16 , slot #n+5 is notavailable for a fourth type repetition since the set of OFDM symbolsdetermined by the value S and the value L overlaps with 9011. In otherwords, slot #n+5 is not available for a fourth type repetition sincesome OFDM symbols determined by the value S and the value L doesn'toverlap with 9002 or 9003.

Before determining a RV for each instance, the terminal device 1 maydetermine whether one or more instances are omitted or not. For example,in a case that no instances are omitted, the terminal device maydetermine that the instance 16001, 16002, and 16003 as the first K,instances. For example, in a case that the instance 16002 is omitted dueto the collision with the high priority signal, the terminal devicedetermines that the instance 16001, 16003 and 16004 as the first K,instances. For example, in a case that the instance 16003 is omitted dueto the collision with the high priority signal, the terminal devicedetermines that the instance 16001, 16002 and 16004 as the first K,instances.

A sequence of RV may be provided for the fourth type repetition to theterminal device 1. For example, the sequence may be provided by a RRClayer through a RRC parameter. In a case that a sequence of RV isprovided for the fourth type repetition, (mod (n, N_(s))+1)^(th) valuein the sequence may be allocated to n^(th) instance within the firstK_(rep) instances. For example, a first sequence of RV and a fourthsequence of RV may be provided to the terminal device 1. For example,the first sequence may be used for a first type repetition. For example,the fourth sequence may be used for a fourth type repetition.

For example, the first sequence may be provided by a RRC layer through afirst RRC parameter. For example, the fourth sequence may be provided bya RRC layer through a fourth RRC parameter which is different from thefirst RRC parameter.

For a fourth type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot configuration, transmission of theinstance may be omitted. On the other hand, for a fourth typerepetition, there may be no case that an instance overlaps with adownlink symbol determined by a slot configuration since the collisionhandling with the downlink symbol by the slot configuration may havebeen done already in a procedure of determining the continuous availableslots. Therefore, for a fourth type repetition, transmission of theinstance may not be omitted based on the slot configuration. Forexample, for a fourth type repetition, the terminal device 1 may notdetermine, based on the slot configuration, whether an instance isomitted or not. For example, the terminal device 1 may not perform aprocess of determining, based on the slot configuration, whether aninstance is omitted or not.

For a fourth type repetition, in a case that an instance overlaps with adownlink symbol determined by a slot format, transmission of theinstance may be omitted.

For a fourth type repetition, in a case that an instance overlaps withanother uplink signal with a higher priority than the priority for thePUSCH, transmission of the instance may be omitted. For example, theuplink signal may be a second PUSCH with higher priority than thepriority of the PUSCH. For example, the priority for a PUSCH may beprovided by a DCI format scheduling the PUSCH.

For a fourth type repetition, the first K p instances are transmittedfor the PUSCH transmission.

FIG. 17 is an example configuration of first type repetition of a PUSCHwith a configured grant in multiple slots according to an aspect of thepresent embodiment. In FIG. 17, 17010 indicates a period for aconfigured grant. 17011 indicates a period for a configured grant.Periods 17010 and 17011 are configured periodically. A configured grantoccurs in a starting OFDM symbol of the period 17010. In a case that aconfigured grant occurs in a starting OFDM symbol of the period 17010,it is assumed that the first type repetition is scheduled in slotsstarting at slot #n+3 where slot #n+3 includes the starting OFDM symbol.17001 indicates an instance of the PUSCH in slot #n+3. Here, a value Sindicates a starting OFDM symbol index within the slot for the instance17001. Also, a value L indicates a length in terms of the number of OFDMsymbols for the instance 17001. 5 instances indicated by 17002 to 17006are followed by the instance 17001. Each instance is mapped within aslot. In FIG. 17 , it is assumed that the number K_(rep) of repetitionsis 6.

Here, the PUSCH is associated with the period 17010. Also, the PUSCH isassociated with the instances 17001 to 17006.

For example, a value S and a value L may be provided by a RRC layer viaa RRC parameter. For example, a value S and a value L may be provided bya TDRA field in a DCI format which activates a configured grantoperation.

17007 indicates an instance of another PUSCH. The instance 17007 is nota part of repetitions for the PUSCH within the period 17010. Theinstance 17007 is a first instance for another PUSCH within the period17011. Here, a period may define a time occasion which includes a numberof repetitions for a single PUSCH. For example, if two instances areincluded in different periods, the two instances are associated withdifferent PUSCH.

Here, another PUSCH is associated with the period 17011. Also, anotherPUSCH is associated with the instances 17001 to 17006.

A PUSCH with instances which occur within a period is associated withthe period. The PUSCH is associated with the instances.

In FIG. 17 , the S is applied to all the instances for the PUSCH. Forexample, all the instances apply the same starting OFDM symbol indexwithin a slot. In FIG. 17 , the L is applied to all the instances forthe PUSCH. For example, all the instances apply the same length in termsof the number of OFDM symbols.

In a first type repetition, multiple instances for a PUSCH may beallocated on K_(rep) continuous slots starting at a slot including astarting OFDM symbol of a period.

FIG. 18 is an example configuration of second type repetition of a PUSCHwith a configured grant in multiple slots according to an aspect of thepresent embodiment. In FIG. 18, 18001 indicates an instance of the PUSCHin slot #n+3. Here, a value S indicates a starting OFDM symbol indexwithin the slot for the instance. Also, a value L indicates a length interms of the number of OFDM symbols for the instance. 2 instancesindicated by 18002 and 18003 are followed by the instance 18001. Eachinstance is mapped within a slot.

In FIG. 18 , it is assumed that the number K_(rep) of repetitions is 4.On the other hand, the instance 18004 is not associated with the PUSCH.The instance 18004 is a first instance associated with another PUSCHwithin the period 17011.

For example, for a second type repetition, a set of instances for aPUSCH associated with a period may be determined based on the numberK_(rep) and the period. For example, in a case that an instance for aPUSCH is out of the period associated with the PUSCH, the instance maybe excluded from the set of instances for the PUSCH. For example, theK_(rep) indicates a maximum value for the number of instances for aPUSCH and instances are mapped within the period such that the number ofthe instances doesn't exceed the number K_(rep).

In FIG. 18 , a value S is applied to all instances for the PUSCH. Forexample, all instances apply the same starting OFDM symbol index withina slot. In FIG. 18 , a value L is applied to all instances for thePUSCH. For example, all instances apply the same length in terms of thenumber of OFDM symbols.

In a second type repetition, the multiple instances for a PUSCH may beallocated on continuous available slots starting at a slot including astarting OFDM symbol of a period associated with the PUSCH.

A third type repetition is described with FIG. 18 assuming K_(rep)=4.

In a third type repetition, multiple instances for a PUSCH may beallocated on continuous available slots starting at a slot including astarting OFDM symbol of the period associated with the PUSCH.

For example, for a third type repetition, a set of instances for a PUSCHassociated with a period may be determined based on the number K_(rep)and the period. For example, in a case that an instance for a PUSCH isout of the period associated with the PUSCH, the instance may beexcluded from the set of instances for the PUSCH. For example, theK_(rep) indicates a maximum value for the number of instances for aPUSCH and instances are mapped within the period such that the number ofthe instances doesn't exceed the number K_(rep).

A fourth type repetition is described with FIG. 16 assuming K_(rep)=4.

In a fourth type repetition, multiple instances for a PUSCH may beallocated on continuous available slots starting at a slot including astarting OFDM symbol of the period associated with the PUSCH.

FIG. 19 shows an example of a method for a UE. The method may compriseacquiring a first RRC parameter (Step 1901) and transmitting a PUSCH inmultiple slots (Step 1902). If the first RRC parameter is set to a firstvalue, conditions in a slot format procedure may not be used fordetermination of the multiple slots. If the first RRC parameter is setto a second value, the conditions in the slot format procedure may beused for the determination of the multiple slots.

FIG. 20 shows an example of a method for a base station is described.The method may comprise sending a first RRC parameter (Step 2001) andreceiving a PUSCH in multiple slots (Step 2002). If the first RRCparameter is set to a first value, conditions in a slot format proceduremay not be used for determination of the multiple slots. If the firstRRC parameter is set to a second value, the conditions in the slotformat procedure may be used for the determination of the multipleslots.

There are two types of transmission without dynamic grant. One is theconfigured grant Type 1 where an uplink grant is provided by RRC, andstored as configured uplink grant, and another is the configured grantType 2 where an uplink grant is provided by PDCCH, and stored or clearedas configured uplink grant based on L1 signalling indicating configureduplink grant activation or deactivation. Type 1 and Type 2 areconfigured by RRC for a Serving Cell per BWP. Multiple configurationscan be active simultaneously in the same BWP. For Type 2, activation anddeactivation are independent among the Serving Cells. For the same BWP,the MAC entity can be configured with both Type 1 and Type 2.

RRC configures the following parameters when the configured grant Type 1is configured. The cs-RNTI is used for determining CS-RNTI forretransmission. The periodicity is used for determining the periodicityof the configured grant Type 1. The timeDomainOffset is used fordetermining the offset of a resource with respect toSFN=timeReferenceSFN in time domain. The timeDomainAllocation is usedfor determining the allocation of configured uplink grant in time domainwhich contains startSymbolAndLength (i.e. SLIV) or startSymbol. ThenrofHARQ-Processes is used for determining the number of HARQ processesfor configured grant. The harq-ProcID-Offset is used for determining theoffset of HARQ process for configured grant for operation with sharedspectrum channel access. The harq-ProcID-Offset2 is used for determiningthe offset of HARQ process for configured grant. The timeReferenceSFN isused for determining the SFN used for determination of the offset of aresource in time domain. The UE uses the closest SFN with the indicatednumber preceding the reception of the configured grant configuration.

RRC configures the following parameters when the configured grant Type 2is configured. The cs-RNTI is used for determining CS-RNTI forretransmission. The periodicity is used for determining the periodicityof the configured grant Type 2. The nrofHARQ-Processes is used fordetermining the number of HARQ processes for configured grant. Theharq-ProcID-Offset is used for determining the offset of HARQ processfor configured grant for operation with shared spectrum channel access.The harq-ProcID-Offset2 is used for determining the offset of HARQprocess for configured grant.

RRC configures the following parameters when retransmissions onconfigured uplink grant is configured. The cg-RetransmissionTimer isused for determining the duration after a configured grant(re)transmission of a HARQ process when the UE may have to notautonomously retransmit that HARQ process.

Upon configuration of a configured grant Type 1 for a BWP of a ServingCell by upper layers, the MAC entity may have to store the uplink grantprovided by upper layers as a configured uplink grant for the indicatedBWP of the Serving Cell and initialise or re-initialise the configureduplink grant to start in the symbol according to timeDomainOffset,timeReferenceSFN, and S (derived from SLIV or provided by startSymbol),and to reoccur with periodicity.

After an uplink grant is configured for a configured grant Type 1, theMAC entity may have to consider sequentially that the Nth (N>=0) uplinkgrant occurs in the symbol for which[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in theslot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

After an uplink grant is configured for a configured grant Type 2, theMAC entity may have to consider sequentially that the Nth (N>=0) uplinkgrant occurs in the symbol for which[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstarttime×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstarttime×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for a configuredgrant Type 1 or Type 2, the MAC entity may have to consider the uplinkgrants occur in those additional PUSCH allocations as specified in theUE procedure(s) for transmitting the PUSCH with the resource allocationfor the uplink transmission with configured grant.

If the available slot-based counting is configured for a configuredgrant Type 1, the MAC entity may have to consider the Nth (N>=0) uplinkgrant occurs in the first symbol of the first available slot asspecified in the UE procedure(s) associated with Transport Blockrepetition for uplink transmissions of PUSCH repetition Type A with aconfigured grant at or after the symbol for which[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in theslot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

If the available slot-based counting is configured for a configuredgrant Type 2, the MAC entity may have to consider the Nth (N>=0) uplinkgrant occurs in the first symbol of the first available slot asspecified in the UE procedure(s) associated with Transport Blockrepetition for uplink transmissions of PUSCH repetition Type A with aconfigured gran at or after the symbol for which[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in theframe×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstarttime×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstarttime×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

The SFNstart time, the slotstart time, and the symbolstart time are theSFN, slot, and symbol, respectively, of the first transmissionopportunity of PUSCH where the configured uplink grant was(re-)initialised.

In case of unaligned SFN across carriers in a cell group, the SFN of theconcerned Serving Cell is used to calculate the occurrences ofconfigured uplink grants.

When the configured uplink grant is released by upper layers, all thecorresponding configurations may have to be released, and allcorresponding uplink grants may have to be cleared.

The MAC entity may have to, if at least one configured uplink grantconfirmation has been triggered and not cancelled and if the MAC entityhas UL resources allocated for new transmission and if, in this MACentity, at least one configured uplink grant is configured byconfiguredGrantConfigToAddModList, instruct the Multiplexing andAssembly procedure to generate a Multiple Entry Configured GrantConfirmation MAC CE. Else, the MAC entity may have to instruct theMultiplexing and Assembly procedure to generate a Configured GrantConfirmation MAC CE. Or, the MAC entity may have to cancel all triggeredconfigured uplink grant confirmation(s).

For a configured grant Type 2, the MAC entity may have to clear theconfigured uplink grant(s) immediately after first transmission ofConfigured Grant Confirmation MAC CE or Multiple Entry Configured GrantConfirmation MAC CE which confirms the configured uplink grantdeactivation.

Retransmissions use repetition of configured uplink grants or receiveduplink grants addressed to CS-RNTI or configured uplink grants withcg-RetransmissionTimer configured.

The MAC entity includes a HARQ entity for each Serving Cell withconfigured uplink (including the case when it is configured withsupplementaryUplink), which maintains a number of parallel HARQprocesses.

The number of parallel UL HARQ processes per HARQ entity is specified inthe physical layer procedures for data.

Each HARQ process supports one TB.

Each HARQ process is associated with a HARQ process identifier. For ULtransmission with UL grant in RA Response or for UL transmission forMSGA payload, HARQ process identifier 0 is used.

When a single DCI is used to schedule multiple PUSCH, the UE is allowedto map generated TB(s) internally to different HARQ processes in case ofLBT failure(s), i.e. UE may transmit a new TB on any HARQ process in thegrants that have the same TBS, the same RV and the NDIs indicate newtransmission.

The maximum number of transmissions of a TB within a bundle of thedynamic grant or configured grant is given by REPETITION_NUMBER. For adynamic grant, REPETITION_NUMBER is set to a value provided by lowerlayers, as specified in the UE procedures associated with the resourceallocation in time domain. For a configured grant, REPETITION_NUMBER isset to a value provided by lower layers, as specified in the UEprocedure(s) for transmitting the PUSCH with the resource allocation forthe uplink transmission with configured grant.

If REPETITION_NUMBER>1, after the first transmission within a bundle, atmost REPETITION_NUMBER−1 HARQ retransmissions follow within the bundle.For both dynamic grant and configured uplink grant, bundling operationrelies on the HARQ entity for invoking the same HARQ process for eachtransmission that is part of the same bundle. Within a bundle, HARQretransmissions are triggered without waiting for feedback from previoustransmission according to REPETITION_NUMBER for a dynamic grant orconfigured uplink grant unless they are terminated as specified in theUE procedure for transmitting the PUSCH. Each transmission within abundle is a separate uplink grant delivered to the HARQ entity.

The K available slots may be configured based on the REPETITION_NUMBER.

If a UE is configured with higher layer parameterpusch-TimeDomainAllocationListForMultiPUSCH, the UE does not expect tobe configured with pusch-AggregationFactor.

FIG. 21 shows an example of a table of an applicable PUSCH time domainresource allocation for common search space and DCI format 0_0 in UEspecific search space.

FIG. 22 shows an example of a table of an applicable PUSCH time domainresource allocation for DCI format 0_1 in UE specific search spacescrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI.

FIG. 23 shows an example of a table of an applicable PUSCH time domainresource allocation for DCI format 0_2 in UE specific search spacescrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI.

FIG. 24 shows an example of a table of a default PUSCH time domainresource allocation A for normal CP. The subcarrier spacing specificvalue j is used in determination of K₂ in conjunction to FIG. 24 , fornormal CP.

FIG. 21 , FIG. 22 and FIG. 23 define which PUSCH time domain resourceallocation configuration to apply. FIG. 21 , FIG. 22 and FIG. 23 is usedfor determination of the resource allocation table to be used for PUSCH.

When the UE is scheduled to transmit a PUSCH with no transport block andwith a CSI report(s) by a ‘CSI request’ field on a DCI, the ‘Time domainresource assignment’ field value m of the DCI provides a row index m+1to the allocated table as defined in FIG. 21 , FIG. 22 , FIG. 23 andFIG. 24 .

For PUSCH repetition Type A, the starting symbol S relative to the startof the slot, and the number of consecutive symbols L counting from thesymbol S allocated for the PUSCH are determined from the start andlength indicator SLIV of the indexed row.

For PUSCH repetition Type B, the starting symbol S relative to the startof the slot, and the number of consecutive symbols L counting from thesymbol S allocated for the PUSCH are provided by startSymbol and lengthof the indexed row of the resource allocation table, respectively.

For PUSCH repetition Type A, the PUSCH mapping type is set to Type A orType B as defined in Precoding and mapping to physical resources asgiven by the indexed row.

For PUSCH repetition Type B, the PUSCH mapping type is set to Type B.

For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCIformat 0_1 or 0_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI,or CS-RNTI with NDI=1, the number of repetitions K is determined as thenumber of repetitions K is equal to numberOfRepetitions ifnumberOfRepetitions is present in the resource allocation table, thenumber of repetitions K is equal to pusch-AggregationFactor elseif theUE is configured with pusch-AggregationFactor, otherwise K=1. The numberof slots used for TBS determination N is equal to 1.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isenabled, the UE determines N*K slots for a PUSCH transmission of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2, based on RRCparameters tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst, and the TDRAinformation field value in the DCI format 0_1 or 0_2. A slot is notcounted in the number of N*K slots for PUSCH transmission of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2 if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst. Otherwise, the UE determines N*K consecutive slotsfor a PUSCH transmission of a PUSCH repetition Type A scheduled by DCIformat 0_1 or 0_2, based on the TDRA information field value in the DCIformat 0_1 or 0_2.

As explained above, there are two counting method, one is available-slotcounting (also referred to as the counting based on available slots) andthe other is physical-slot counting (also referred to as the countingbased on consecutive slots, consecutive-slot counting orregular/normal/legacy counting). In the available-slot counting, the N*Kearliest available slots no earlier than the slot which is determined bythe slot offset K2 may be determined as the slots for a PUSCHtransmission, where a slot is not counted as the available slot if atleast one of the symbols indicated by the indexed row of the usedresource allocation table (i.e., the symbols indicated by the TDRAfield) in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst. In the physical-slot counting, the N*K consecutiveslots starting with the slot which is determined by the slot offset K2may be determined as the slots for a PUSCH transmission, irrespective ofthe overlapping with the DL symbol or the symbol of the SS/PBCH block.Note that the actual transmission in the slot determined for the PUSCHmay or may not be further dropped depending on the collisions with otherchannels and/or signals.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isenabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K consecutive slots for a PUSCH transmission of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2, based on the TDRAinformation field value in the DCI format 0_1 or 0_2.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isenabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K consecutive slots for a PUSCH transmission with atransport block of a PUSCH repetition Type A scheduled by DCI format 0_1or 0_2, based on the TDRA information field value in the DC format 0_1or 0_2.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isdisabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K consecutive slots for a PUSCH transmission of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2, based on the TDRAinformation field value in the DCI format 0_1 or 0_2.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isdisabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K consecutive slots for a PUSCH transmission with atransport block of a PUSCH repetition Type A scheduled by DCI format 0_1or 0_2, based on the TDRA information field value in the DCI format 0_1or 0_2.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isenabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K slots for a PUSCH transmission of a PUSCH repetitionType A scheduled by DCI format 0_1 or 0_2, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst, and the TDRA information field value in the DCIformat 0_1 or 0_2. A slot may be not counted in the number of the N*Kslots for the PUSCH transmissions with a transport block of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2 if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst.

For unpaired spectrum, when an RRC parameter AvailableSlotCounting isdisabled and the UE is scheduled to transmit a PUSCH with no transportblock and with a CSI report(s) by a ‘CSI request’ field on a DCI, the UEmay determine N*K slots for a PUSCH transmission of a PUSCH repetitionType A scheduled by DCI format 0_1 or 0_2, based on RRC parameterstdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated andssb-PositionsInBurst, and the TDRA information field value in the DCIformat 0_1 or 0_2. A slot may be not counted in the number of the N*Kslots for the PUSCH transmissions with a transport block of a PUSCHrepetition Type A scheduled by DCI format 0_1 or 0_2 if at least one ofthe symbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated ifprovided, or a symbol of an SS/PBCH block with index provided byssb-PositionsInBurst.

For unpaired spectrum, the UE determines N*K slots for a PUSCHtransmission of TB processing over multiple slots scheduled by DCIformat 0_1 or 0_2, based on tdd-UL-DL-ConfigurationCommon,tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst, and the TDRAinformation field value in the DCI format 0_1 or 0_2. A slot is notcounted in the number of N*K slots for a PUSCH transmission of TBprocessing over multiple slots if at least one of the symbols indicatedby the indexed row of the used resource allocation table in the slotoverlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst.

For unpaired spectrum, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A scheduled by RAR UL grant,based on tdd-UL-DL-ConfigurationCommon and ssb-PositionsInBurst, and theTDRA information field value in the RAR UL grant. A slot is not countedin the number of N*K slots for a PUSCH transmission of a PUSCHrepetition Type A scheduled by RAR UL grant, if at least one of thesymbols indicated by the indexed row of the used resource allocationtable in the slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst.

For unpaired spectrum, the UE determines N*K slots for a PUSCHtransmission of a PUSCH repetition Type A scheduled by DCI format 0_0with CRC scrambled by TC-RNTI, based on tdd-UL-DL-ConfigurationCommonand ssb-PositionsInBurst and the TDRA information field value in the DCIscheduling the PUSCH. A slot is not counted in the number of N*K slotsfor a PUSCH transmission of a PUSCH repetition Type A scheduled by DCIformat 0_0 scrambled by TC-RNTI, if at least one of the symbolsindicated by the indexed row of the used resource allocation table inthe slot overlaps with a DL symbol indicated bytdd-UL-DL-ConfigurationCommon if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst.

For paired spectrum and SUL band, the UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition Type A scheduled byDCI format 0_1 or 0_2, or for a PUSCH transmission of TB processing overmultiple slots scheduled by DCI format 0_1 or 0_2, based on the TDRAinformation field value in the DCI format 0_1 or 0_2, irrespective ofwhether an RRC parameter AvailableSlotCounting is enabled or not. Forthe case of reduced capability half-duplex UE, and when an RRC parameterAvailableSlotCounting is enabled, a slot is not counted in the number ofN*K slots for a PUSCH transmission of a PUSCH repetition Type Ascheduled by DCI format 0_1 or 0_2, or for a PUSCH transmission of TBprocessing over multiple slots scheduled by DCI format 0_1 or 0_2, if atleast one of the symbols indicated by the indexed row of the usedresource allocation table in the slot overlaps with a symbol of anSS/PBCH block with index provided by ssb-PositionsInBurst.

For paired spectrum and SUL band, the UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition Type A scheduled byRAR UL grant, based on the TDRA information field value in the RAR ULgrant.

For paired spectrum and SUL band, the UE determines N*K consecutiveslots for a PUSCH transmission of a PUSCH repetition Type A scheduled byDCI format 0_0 with CRC scrambled by TC-RNTI, based on the TDRAinformation field value in the DCI scheduling the PUSCH.

If an RRC parameter AvailableSlotCounting is enabled and a UE wouldtransmit a PUSCH of a TB processing over multiple slots or PUSCHrepetition Type A over N*K slots, and the UE does not transmit the PUSCHof a TB processing over multiple slots or the PUSCH repetition Type A ina slot from the N*K slots, according to UE procedure(s) for reportingcontrol information, UE procedure(s) associated with a slotconfiguration and UE procedure(s) associated with a cancellationindication, the UE counts the slots in the number of N*K slots.

For PUSCH repetition Type A, in case K>1, if the PUSCH is scheduled byDCI format 0_1 or 0_2, if an RRC parameter AvailableSlotCounting isenabled, the same symbol allocation is applied across the N*K slotsdetermined for the PUSCH transmission and the PUSCH is limited to asingle transmission layer. The UE may have to repeat the TB across theN*K slots determined for the PUSCH transmission, applying the samesymbol allocation in each slot. Otherwise, the same symbol allocation isapplied across the N*K consecutive slots and the PUSCH is limited to asingle transmission layer. The UE may have to repeat the TB across theN*K consecutive slots applying the same symbol allocation in each slot.Else if the PUSCH is scheduled by RAR UL grant or by DCI format 0_0 withCRC scrambled by TC-RNTI, the same symbol allocation is applied acrossthe N*K slots determined for the PUSCH transmission and the PUSCH islimited to a single transmission layer. The UE may have to repeat the TBacross the N*K slots determined for the PUSCH transmission, applying thesame symbol allocation in each slot.

For TB processing over multiple slots, for unpaired spectrum, the samesymbol allocation is applied across the N*K slots determined for thePUSCH transmission and the PUSCH is limited to a single transmissionlayer. The UE may have to transmit the TB across the N*K slotsdetermined for the PUSCH transmission, applying the same symbolallocation in each slot. For paired spectrum or supplementary uplinkband, the same symbol allocation is applied across the N*K consecutiveslots and the PUSCH is limited to a single transmission layer. The UEmay have to transmit the TB across the N*K consecutive slots applyingthe same symbol allocation in each slot.

For a PUSCH transmission scheduled by DCI format 0_1, or 0_2, or 0_0with CRC scrambled by TC-RNTI, the redundancy version to be applied onthe nth transmission occasion of the TB, where n=0, 1, . . . N*K−1, isdetermined according to FIG. 25 .

For a PUSCH transmission of a PUSCH repetition Type A scheduled by RARUL grant, the redundancy version to be applied on the nth transmissionoccasion of the TB, where n=0, 1, . . . N*K−1, is determined accordingto the first row of FIG. 25 .

For PUSCH repetition Type A and TB processing over multiple slots, aPUSCH transmission in a slot of a multi-slot PUSCH transmission isomitted according to the conditions in UE procedure(s) for reportingcontrol information, UE procedure(s) associated with a slotconfiguration and UE procedure(s) associated with a cancellationindication.

For PUSCH repetition Type B, after determining the invalid symbol(s) forPUSCH repetition Type B transmission for each of the K nominalrepetitions, the remaining symbols are considered as potentially validsymbols for PUSCH repetition Type B transmission. If the number ofpotentially valid symbols for PUSCH repetition Type B transmission isgreater than zero for a nominal repetition, the nominal repetitionconsists of one or more actual repetitions, where each actual repetitionconsists of a consecutive set of all potentially valid symbols that canbe used for PUSCH repetition Type B transmission within a slot. Anactual repetition with a single symbol is omitted except for the case ofL=1. An actual repetition is omitted according to the conditions in UEprocedure(s) for reporting control information, UE procedure(s)associated with a slot configuration and UE procedure(s) associated witha cancellation indication. The UE may have to repeat the TB acrossactual repetitions. The redundancy version to be applied on the nthactual repetition (with the counting including the actual repetitionsthat are omitted) is determined according to FIG. 25 , where N=1.

For PUSCH repetition Type B, when a UE receives a DCI that schedulesaperiodic CSI report(s) or activates semi-persistent CSI report(s) onPUSCH with no transport block by a ‘CSI request’ field on a DCI, thenumber of nominal repetitions is always assumed to be 1, regardless ofthe value of numberOfRepetitions. When the UE is scheduled to transmit aPUSCH repetition Type B with no transport block and with aperiodic orsemi-persistent CSI report(s) by a ‘CSI request’ field on a DCI, thefirst nominal repetition is expected to be the same as the first actualrepetition. For PUSCH repetition Type B carrying semi-persistent CSIreport(s) without a corresponding PDCCH after being activated on PUSCHby a ‘CSI request’ field on a DCI, if the first nominal repetition isnot the same as the first actual repetition, the first nominalrepetition is omitted; otherwise, the first nominal repetition isomitted according to the conditions in UE procedure(s) for reportingcontrol information, UE procedure(s) associated with a slotconfiguration and UE procedure(s) associated with a cancellationindication.

For PUSCH repetition Type B, when a UE is scheduled to transmit atransport block and aperiodic CSI report(s) on PUSCH by a ‘CSI request’field on a DCI, the CSI report(s) is multiplexed only on the firstactual repetition. The UE does not expect that the first actualrepetition has a single symbol duration.

If pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config containsrow indicating resource allocation for two to eight contiguous PUSCHs,K2 indicates the slot where UE may have to transmit the first PUSCH ofthe multiple PUSCHs. Each PUSCH has a separate SLIV and mapping type.The number of scheduled PUSCHs is signalled by the number of indicatedvalid SLIVs in the row of thepusch-TimeDomainAllocationListForMultiPUSCH signalled in DCI format 0_1.

For pusch-TimeDomainAllocationListForMultiPUSCH-r17 in pusch-Config,each PUSCH has a separate SLIV, mapping type and K2. The number ofscheduled PUSCHs is signalled by the number of indicated SLIVs in therow of the pusch-TimeDomainAllocationListForMultiPUSCH-r17 signalled inDCI format 0_1.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for unpaired spectrum, if an RRC parameterAvailableSlotCounting is enabled, the UE may have to repeat the TBacross the N*K slots determined for the PUSCH transmission applying thesame symbol allocation in each slot. A slot is not counted in the numberof N−K slots if at least one of the symbols indicated by the indexed rowof the used resource allocation table in the slot overlaps with a DLsymbol indicated by tdd-UL-DL-ConfigurationCommon ortdd-UL-DL-ConfigurationDedicated if provided, or a symbol of an SS/PBCHblock with index provided by ssb-PositionsInBurst. Otherwise, the UE mayhave to repeat the TB across the N*K consecutive slots applying the samesymbol allocation in each slot, except if the UE is provided with higherlayer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case theUE repeats the TB in the repK earliest consecutive transmission occasioncandidates within the same configuration.

For both Type 1 and Type 2 PUSCH transmissions with a configured grant,when K>1, for paired spectrum, irrespective of whetherAvailableSlotCounting is enabled or not, the UE may have to repeat theTB across the N*K consecutive slots applying the same symbol allocationin each slot, except if the UE is provided with RRC parameterscg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats theTB in the repK earliest consecutive transmission occasion candidateswithin the same configuration. If an RRC parameter AvailableSlotCountingis enabled, and in case of reduced capability half-duplex UE, a slot isnot counted in the number of N*K slots if at least one of the symbolsindicated by the indexed row of the used resource allocation table inthe slot overlaps with or a symbol of an SS/PBCH block with indexprovided by ssb-PositionsInBurst.

A Type 1 or Type 2 PUSCH transmission with a configured grant in a slotis omitted according to the conditions in UE procedure(s) for reportingcontrol information, UE procedure(s) associated with a slotconfiguration and UE procedure(s) associated with a cancellationindication.

For the PUSCH without UL-SCH and/or the PUSCH with CSI only, N=1 and K=1may be assumed in the aforementioned procedure. A UE and a base stationfor this case are described.

The UE may comprise high-layer processing circuitry configured toacquire at least a first RRC parameter for indicating whetheravailable-slot counting is enabled or not. The first RRC parameter maybe named AvailableSlotCounting. The possible values of the first RRCparameter may be “enabled” and “disabled”. The UE may also comprisereception circuitry configured to receive a DCI format (e.g., DCI format0_1 or DCI format 0_2) for scheduling of a PUSCH. This may also bedescribed as that the reception circuitry may monitor and detect a PDCCHwhich carries the DCI format. The UE may also comprise transmissioncircuitry configured to transmit the PUSCH in one or more slotsscheduled by the DCI format. The UE may transmit the PUSCH upon thedetection of the PDCCH with the DCI format which schedules the PUSCH.

A base station which communicates with the UE may comprise thefunctional units associated with the functional units at the UE side andmay perform the processes associated with the processes at the UE side.The base station (also referred to as gNB) may comprise high-layerprocessing circuitry configured to send at least a first RRC parameterfor indicating whether available-slot counting is enabled or not. Thebase station may also comprise transmission circuitry configured totransmit a DCI format (e.g., DCI format 0_1 or DCI format 0_2) forscheduling of a PUSCH. This may also be described as that thetransmission circuitry may transmit a PDCCH which carries the DCIformat. The base station may also comprise reception circuitryconfigured to receive the PUSCH in one or more slots scheduled by theDCI format. The base station may monitor and receive the PUSCH upon thetransmission of the PDCCH with the DCI format which schedules the PUSCH.

The DCI format may include a plurality of information fields. Theplurality of information fields may include Time domain resourceassignment field (also referred to as TDRA (time domain resourceallocation) field). The plurality of information fields may include CSIrequest field. The plurality of information fields may include UL-SCHindicator field. A trigger state may be initiated using the CSI requestfield in DCI. When all the bits of CSI request field in DCI are set tozero, no CSI is requested. Each of the other values of the CSI requestfield in DCI may correspond to and indicate a respective triggeringstate. Each trigger state may contain a list of associatedCSI-ReportConfigs indicating the Resource Set IDs for channel andoptionally for interference. A value of “1” set in the UL-SCH indicatorfield may indicate UL-SCH is to be transmitted on the PUSCH and a valueof “0” in the UL-SCH indicator field may indicate UL-SCH is not to betransmitted on the PUSCH. In other words, a value of “1” set in theUL-SCH indicator field may indicate at least one transport block is tobe included in the PUSCH, and a value of “0” set in the UL-SCH indicatorfield may indicate no transport block is to be included in the PUSCH.The value of the UL-SCH indicator field may be set to “0” only when atrigger state except for no CSI request is initiated using the CSIrequest field in the DCI.

In a case that the first RRC parameter indicates that the available-slotcounting is enabled and the PUSCH is transmitted in unpaired spectrum,the UE may determine whether to use available-slot counting, based on ametric. The metric may be whether a transport block is included in thePUSCH or not. For example, the available-slot counting is used if atransport block is included on the PUSCH, and the physical-slot countingis used if a transport block is not included on the PUSCH. In otherwords, the UE may determine whether a first slot where at least one ofsymbols indicated by a TDRA field overlaps with a DL symbol or a symbolof an SS/PBCH block is not counted as a second slot for a transmissionof the PUSCH or not, based on whether a transport block is included onthe PUSCH or not. For example, the first slot is not counted as thesecond slot if a transport block is included on the PUSCH, and the firstslot is counted as the second slot if a transport block is not includedon the PUSCH.

Alternatively or additionally, the metric may be whether the value ofthe UL-SCH index field is set to “1” or “0”. For example, theavailable-slot counting is used if the value of the UL-SCH index fieldin the DCI is set to “1”, and the physical-slot counting is used if thevalue of the UL-SCH index field in the DCI is set to “0”.

Yet alternatively or additionally, the metric may be whether the valueof the CSI request field indicates another trigger state than no CSIrequest or not. For example, the available-slot counting is used if thevalue of the CSI request field indicates another trigger state than noCSI request, and the physical-slot counting is used if the value of theCSI request field indicates the state corresponding to no CSI request.

Yet alternatively or additionally, the metric may be whether the PUSCHis for CSI only or not. For example, the available-slot counting is usedif the PUSCH is not for CSI only, and the physical-slot counting is usedif the PUSCH is for CSI only.

These methods may lead to a unified processing for the CSI-only PUSCHtransmissions with and without AvailableSlotCounting configuration, andtherefore the processing complexity in terms of aperiodic CSI reportingmay be reduced.

In a case that the high-layer processing circuitry does not acquire thefirst RRC parameter which indicates that the available-slot counting isenabled, the UE may always use the physical-slot counting. In otherwords, in a case that the high-layer processing circuitry does notacquire the first RRC parameter which indicates that the available-slotcounting is enabled, the UE may determine the first slot is counted asthe second slot, regardless of whether a transport block is included onthe PUSCH or not. In a case that the PUSCH is transmitted in pairedspectrum, the UE may always use the physical-slot counting. In otherwords, in a case that the PUSCH is transmitted in paired spectrum, theUE may determine the first slot is counted as the second slot,regardless of whether a transport block is included on the PUSCH or not.

As an alternative way, in a case that the first RRC parameter indicatesthat the available-slot counting is enabled and the PUSCH is transmittedin unpaired spectrum, the UE may use available-slot counting fordetermination of a slot for a transmission of the PUSCH without atransport block and with an aperiodic CSI report. This is the same asfor a transmission of the PUSCH with a transport block and with anaperiodic CSI report or for a multi-slot transmission of the PUSCH witha transport block.

This method may lead to a unified processing for available-slot countingfor the PUSCH transmission with a transport block and the CSI-only PUSCHtransmission, and therefore the processing complexity in terms of slotcounting may be reduced.

More details of UE procedure(s) for applying transform precoding onPUSCH are described.

For a PUSCH scheduled by RAR UL grant, or for a PUSCH scheduled byfallbackRAR UL grant, or for a PUSCH scheduled by DCI format 0_0 withCRC scrambled by TC-RNTI, the UE shall consider the transform precodingeither ‘enabled’ or ‘disabled’ according to the higher layer configuredparameter msg3-transformPrecoder.

For a MsgA PUSCH, the UE shall consider the transform precoding either‘enabled’ or ‘disabled’ according to the higher layer configuredparameter msgA-TransformPrecoder. If an RRC parametermsgA-TransformPrecoder is not configured, the UE shall consider thetransform precoding either ‘enabled’ or ‘disabled’ according to the RRCparameter msg3-transformPrecoder.

The RRC parameter msgA-TransformPrecoder indicates whether the UEenables or disables the transform precoder for MsgA transmission.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was received with DCI format 0_0, the UEshall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to the RRC parametermsg3-transformPrecoder.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, and ifthe UE is configured with the RRC parameter transformPrecoder inpusch-Config, the UE shall, for this PUSCH transmission, consider thetransform precoding either enabled or disabled according to thisparameter (i.e. configured transformPrecoder).

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, and ifthe UE is configured with the RRC parameters transformPrecoder anddynamicSwitchingTransformPrecoder set to ‘disabled’ in pusch-Config, theUE shall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to the RRC parametertransformPrecoder.

“The DCI with the scheduling grant was not received with DCI format 0_0”may mean that “the DCI with the scheduling grant was received with a DCIformat other than the DCI format 0_0”. Or “the DCI with the schedulinggrant was not received with DCI format 0_0” may mean that “thescheduling grant was received with a configured grant”.

The RRC parameter dynamicSwitchingTransformPrecoder indicates whether ornot the ‘transform precoding indicator’ field is included in the DCIformat 0_1/0_2. The ‘transform precoding indicator’ field is used forindicating whether or not the transform precoder is enabled.

The RRC parameter dynamicSwitchingTransformPrecoder may be configured asa common parameter for different DCI formats.

The RRC parameter dynamicSwitchingTransformPrecoder may be configuredfor the DCI format 0_1 and the DCI format 0_2, respectively. In otherwords, the RRC parameter dynamicSwitchingTransformPrecoder correspondingto each of DCI formats may be configured. If the UE is configured withthe RRC parameters dynamicSwitchingTransformPrecoder corresponding toeach of DCI formats, the UE may assume that he ‘transform precodingindicator’ field may be included in the corresponding DCI format(s),respectively.

If the RRC parameter dynamicSwitchingTransformPrecoder indicates‘enabled’, the ‘transform precoding indicator’ field may be included inthe DCI format 0_1/0_2. If the RRC parameterdynamicSwitchingTransformPrecoder indicates ‘disabled’, the ‘transformprecoding indicator’ field may not be included in the DCI format0_1/0_2.

If the RRC parameter dynamicSwitchingTransformPrecoder is configured,the UE may assume that the ‘transform precoding indicator’ field may beincluded in the DCI format 0_1/0_2. The RRC parameterdynamicSwitchingTransformPrecoder may indicate that the ‘transformprecoding indicator’ field is included in the DCI format 0_1/0_2, ifprovided.

If the RRC parameter dynamicSwitchingTransformPrecoder is notconfigured/absent, the UE may assume that the ‘transform precodingindicator’ field may not be included in the DCI format 0_1/0_2.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, and ifthe UE is configured with the RRC parameters transformPrecoder anddynamicSwitchingTransformPrecoder set to ‘enabled’ in pusch-Config, theUE shall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to the DCI ‘transform precodingindicator’ field.

Alternatively, for PUSCH transmission scheduled by a PDCCH with CRCscrambled by CS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI,if the DCI with the scheduling grant was not received with DCI format0_0, and if the UE is configured with the RRC parameterstransformPrecoder and dynamicSwitchingTransformPrecoder set to ‘enabled’in pusch-Config, the UE shall, for this PUSCH transmission, consider thetransform precoding either enabled or disabled according to the DCI‘transform precoding indicator’ field, irrespective of the value of thetransformPrecoder.

Alternatively, for PUSCH transmission scheduled by a PDCCH with CRCscrambled by CS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI,if the DCI with the scheduling grant was not received with DCI format0_0, and if the UE is configured with the RRC parameterstransformPrecoder set to ‘enabled’ and dynamicSwitchingTransformPrecoderset to ‘enabled’ in pusch-Config, the UE shall, for this PUSCHtransmission, consider the transform precoding either enabled ordisabled according to the DCI ‘transform precoding indicator’ field.

The UE may assume that the DCI ‘transform precoding indicator’ field isnot included in the DCI format 0_0.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, and ifthe UE is not configured with the RRC parameter transformPrecoder inpusch-Config, the UE shall, for this PUSCH transmission, consider thetransform precoding either enabled or disabled according to the RRCparameter msg3-transformPrecoder.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0 and ifthe UE is not configured with the RRC parameters transformPrecoder anddynamicSwitchingTransformPrecoder set to ‘enabled’ in pusch-Config, theUE shall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to the higher layer configuredparameter msg3-transformPrecoder.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0 and ifthe UE is not configured with the RRC parameters transformPrecoder anddynamicSwitchingTransformPrecoder in pusch-Config, the UE shall, forthis PUSCH transmission, consider the transform precoding either enabledor disabled according to the higher layer configured parametermsg3-transformPrecoder.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, if theUE is not configured with the RRC parameters transformPrecoder and ifthe UE is configured with dynamicSwitchingTransformPrecoder set to‘disabled’ in pusch-Config, the UE shall, for this PUSCH transmission,consider the transform precoding either enabled or disabled according tothe RRC parameter msg3-transformPrecoder.

For PUSCH transmission scheduled by a PDCCH with CRC scrambled byCS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI, if the DCIwith the scheduling grant was not received with DCI format 0_0, and ifthe UE is not configured with the RRC parameter transformPrecoder inpusch-Config and if the UE is configured with the RRC parameterdynamicSwitchingTransformPrecoder set to ‘enabled’ in pusch-Config, theUE shall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to the DCI ‘transform precodingindicator’ field.

The feature of the DCI ‘transform precoding indicator’ field may berealized by using the DCI field other than ‘transform precodingindicator’ field. In other words, if the UE is configured with the RRCparameter dynamicSwitchingTransformPrecoder set to ‘enabled’ inpusch-Config, a first value of a first DCI field may indicate that thetransform precoder is enabled, and a second value of the first DCI fieldmay indicate that the transform precoder is disabled. The UE may assumethat the value(s) of the first DCI field included in the DCI format areassociated with whether or not the transform precoder is enabled.

If the base station provides the RRC parameterdynamicSwitchingTransformPrecoder set to ‘enabled’ in pusch-Config, afirst value of a first DCI field may be set for indicating that thetransform precoder is enabled, and a second value of the first DCI fieldmay be set for indicating that the transform precoder is disabled.

For PUSCH transmission with a configured grant, if the UE is configuredwith the RRC parameter transformPrecoder in configuredGrantConfig, theUE shall, for this PUSCH transmission, consider the transform precodingeither enabled or disabled according to this parameter.

For PUSCH transmission with a configured grant, if the UE is notconfigured with the RRC parameter transformPrecoder inconfiguredGrantConfig, the UE shall, for this PUSCH transmission,consider the transform precoding either enabled or disabled according tothe higher layer configured parameter msg3-transformPrecoder.

Here, “the dynamicSwitchingTransformPrecoder is configured” may have asame meaning as “the dynamicSwitchingTransformPrecoder set to ‘enabled’is configured”. And “the dynamicSwitchingTransformPrecoder is notconfigured” may have a same meaning as “thedynamicSwitchingTransformPrecoder set to ‘disabled’ is configured”.

If the UE is capable of applying transform precoding based on a firstDCI field indicating whether a transform precoder is enabled or disabledand the UE is configured with a first RRC parameter indicating that theDCI format 0_1 and/or 0_2 include the first DCI field, the UE may assumethe number of bits for each of one or more DCI fields based on whetheror the first DCI field is included in the DCI format(s) and may monitorthe DCI format(s) based on the assumption. For example, the number ofbits for each of the precoding information and number of layers field,the second precoding information field, the antenna ports field, thePTRS-DMRS association field, the second PTRS-DMRS association fieldand/or DMRS sequence initialization field may be determined based onwhether or not the UE is configured with a first RRC parameterindicating that the DCI format 0_1 and/or 0_2 include the first DCIfield.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2 (i.e., corresponding to the DCI format), the DCI size (i.e., numberof bits) and/or the applied table of one or more DCI fields other thanthe transform precoding indicator field may be determined. One of theone or more DCI fields may be the precoding information and number oflayers field. One of the one or more DCI fields may be the secondprecoding information field. One of the one or more DCI fields may bethe antenna ports field. One of the one or more DCI fields may be thePTRS-DMRS association field. One of the one or more DCI fields may bethe second PTRS-DMRS association field. One of the one or more DCIfields may be the DMRS sequence initialization field. The UE may monitorthe DCI field(s) based on the assumption. The base station may set theDCI size (number of bits) for each of the DCI fields based on theassumption if the RRC parameter dynamicSwitchingTransformPrecoderindicates that the transform precoding indicator field is included inthe DCI format 0_1 and/or the DCI format 0_2.

In other words, each DCI size of the associated DCI fields may bedetermined/assumed based on whether or not the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the precoding information and number of layersfield may be maximum number of one or more bits according to the tablesapplied based on the values of the RRC parameters txConfig,ul-FullPowerTransmission, maxRank, and codebookSubset for the DCI format0_1 or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2, andnumber of antenna ports and by considering that the transform precoderis enabled and disabled.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the second precoding information field may bemaximum number of one or more bits according to the tables applied basedon the values of the RRC parameters txConfig, ul-FullPowerTransmission,maxRank, and codebookSubset for the DCI format 0_1 or maxRankDCI-0-2 andcodebookSubsetDCI-0-2 for DCI format 0_2, and number of antenna portsand the same number of layers indicated by the precoding information andnumber of layers field and by considering that the transform precoder isenabled and disabled.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the antenna ports field may be maximum number ofone or more bits according to the tables applied based on one or moreconditions according to whether transform precoder is enabled ordisabled, the value of rank, the values of the RRC parameters dmrs-Type,maxLength, txConfig, dmrs-UplinkTransformPrecoding and tp-pi2BPSK.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for [0626]

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the PTRS-DMRS association field may be 2 bits.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the second PTRS-DMRS association field may be 2bits.

For example, if the configured RRC parameterdynamicSwitchingTransformPrecoder indicates that the transform precodingindicator field is included in the DCI format 0_1 and/or the DCI format0_2, number of bits for the DMRS sequence initialization field may be 1bits.

If the configured RRC parameter dynamicSwitchingTransformPrecoderindicates that the transform precoding indicator field is included inthe DCI format 0_1 and/or the DCI format 0_2, number of bits for any ofthe precoding information and number of layers field, the secondprecoding information field, and/or the antenna ports field may bedetermined/assumed according to the new table.

If the configured RRC parameter dynamicSwitchingTransformPrecoderindicates that the transform precoding indicator field is included inthe DCI format 0_1 and/or the DCI format 0_2 and different number ofbits based on whether the transform precoder is enabled or disabled, theextra bit(s) not used for the table may be consider as the paddingbit(s).

If the configured RRC parameter dynamicSwitchingTransformPrecoder doesnot indicate that the transform precoding indicator field is included inthe DCI format 0_1 and/or the DCI format 0_2, the number of bits foreach of the DCI fields may be determined/assumed based on whether theRRC parameter transformPrecoder is enabled or disabled (e.g., existingdetermination method).

Each of a program running on the base station device and the terminaldevice according to an aspect of the present invention may be a programthat controls a Central Processing Unit (CPU) and the like, such thatthe program causes a computer to operate in such a manner as to realizethe functions of the above-described embodiment according to the presentinvention. The information handled in these devices is transitorilystored in a Random-Access-Memory (RAM) while being processed.Thereafter, the information is stored in various types ofRead-Only-Memory (ROM) such as a Flash ROM and a Hard-Disk-Drive (HDD),and when necessary, is read by the CPU to be modified or rewritten.

Note that the terminal device 1 and the base station device 3 accordingto the above-described embodiment may be partially achieved by acomputer. In this case, this configuration may be realized by recordinga program for realizing such control functions on a computer-readablerecording medium and causing a computer system to read the programrecorded on the recording medium for execution.

Note that it is assumed that the “computer system” mentioned here refersto a computer system built into the terminal device 1 or the basestation device 3, and the computer system includes an OS and hardwarecomponents such as a peripheral device. Furthermore, the“computer-readable recording medium” refers to a portable medium such asa flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like,and a storage device built into the computer system such as a hard disk.

Moreover, the “computer-readable recording medium” may include a mediumthat dynamically retains a program for a short period of time, such as acommunication line that is used to transmit the program over a networksuch as the Internet or over a communication line such as a telephoneline, and may also include a medium that retains a program for a fixedperiod of time, such as a volatile memory within the computer system forfunctioning as a server or a client in such a case. Furthermore, theprogram may be configured to realize some of the functions describedabove, and also may be configured to be capable of realizing thefunctions described above in combination with a program already recordedin the computer system.

Furthermore, the base station device 3 according to the above-describedembodiment may be achieved as an aggregation (an device group) includingmultiple devices. Each of the devices configuring such an device groupmay include some or all of the functions or the functional blocks of thebase station device 3 according to the above-described embodiment. Thedevice group may include each general function or each functional blockof the base station device 3. Furthermore, the terminal device 1according to the above-described embodiment can also communicate withthe base station device as the aggregation.

Furthermore, the base station device 3 according to the above-describedembodiment may serve as an Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) and/or NG-RAN (Next Gen RAN, NR-RAN). Furthermore, thebase station device 3 according to the above-described embodiment mayhave some or all of the functions of a node higher than an eNodeB or thegNB.

Furthermore, some or all portions of each of the terminal device 1 andthe base station device 3 according to the above-described embodimentmay be typically achieved as an LSI which is an integrated circuit ormay be achieved as a chip set. The functional blocks of each of theterminal device 1 and the base station device 3 may be individuallyachieved as a chip, or some or all of the functional blocks may beintegrated into a chip. Furthermore, a circuit integration technique isnot limited to the LSI, and may be realized with a dedicated circuit ora general-purpose processor. Furthermore, in a case that with advancesin semiconductor technology, a circuit integration technology with whichan LSI is replaced appears, it is also possible to use an integratedcircuit based on the technology.

Furthermore, according to the above-described embodiment, the terminaldevice has been described as an example of a communication device, butthe present invention is not limited to such a terminal device, and isapplicable to a terminal device or a communication device of afixed-type or a stationary-type electronic device installed indoors oroutdoors, for example, such as an Audio-Video (AV) device, a kitchendevice, a cleaning or washing machine, an air-conditioning device,office equipment, a vending machine, and other household devices.

The embodiments of the present invention have been described in detailabove referring to the drawings, but the specific configuration is notlimited to the embodiments and includes, for example, an amendment to adesign that falls within the scope that does not depart from the gist ofthe present invention. Furthermore, various modifications are possiblewithin the scope of one aspect of the present invention defined byclaims, and embodiments that are made by suitably combining technicalmeans disclosed according to the different embodiments are also includedin the technical scope of the present invention. Furthermore, aconfiguration in which constituent elements, described in the respectiveembodiments and having mutually the same effects, are substituted forone another is also included in the technical scope of the presentinvention.

1. A user equipment (UE) comprising: high-layer processing circuitryconfigured to acquire at least a first RRC parameter for indicatingtxConfig and a second RRC parameter for indicating whether or not atransform precoding indicator field is included in a DCI format,reception circuitry configured to receive the DCI format for schedulingof a PUSCH, and transmission circuitry configured to transmit the PUSCHscheduled by the DCI format, wherein in a case that the first RRCparameter indicates codebook and the second RRC parameter indicates thatthe transform precoding indicator field is included in the DCI format,the reception circuitry is configured to monitor the DCI formatincluding a first DCI field with a maximum number of bits among one ormore tables applied based on values of a third RRC parameter, a fourthRRC parameter, a fifth RRC parameter, a sixth RRC parameter and atransform precoder.
 2. The UE of claim 1, wherein in a case that thefirst RRC parameter indicates codebook and the second RRC parameterindicates that the transform precoding indicator field is included inthe DCI format, the reception circuitry is configured to assume thetable based on values of the third RRC parameter, the fourth RRCparameter, the fifth RRC parameter, the sixth RRC parameter and thetransform precoding indicator field.
 3. The UE of claim 1, wherein in acase that the first RRC parameter indicates enabled and the second RRCparameter indicates that the transform precoding indicator field isincluded in the DCI format, the transmission circuitry is configured toapply a transform precoding for a transmission of the PUSCH, based onthe value of the transform precoding indicator field in the DCI format.4. A base station comprising: higher-layer processing circuitryconfigured to provide at least a first RRC parameter for indicatingtxConfig and a second RRC parameter for indicating whether or not atransform precoding indicator field is included in a DCI format,transmission circuitry configured to transmit the DCI format forscheduling of a PUSCH, and reception circuitry configured to receive thePUSCH scheduled by the DCI format, wherein in a case that the first RRCparameter indicates codebook and the second RRC parameter indicates thatthe transform precoding indicator field is included in the DCI format,the transmission circuitry is configured to set the DCI format includinga first DCI field with a maximum number of bits among one or more tablesapplied based on values of a third RRC parameter, a fourth RRCparameter, a fifth RRC parameter, a sixth RRC parameter and a transformprecoder.
 5. A method for a user equipment, the method comprising:acquiring at least a first RRC parameter for indicating txConfig and asecond RRC parameter for indicating whether or not a transform precodingindicator field is included in a DCI format, receiving the DCI formatfor scheduling of a PUSCH, and transmitting the PUSCH scheduled by theDCI format, wherein monitoring the DCI format including a first DCIfield with a maximum number of bits among one or more tables appliedbased on values of a third RRC parameter, a fourth RRC parameter, afifth RRC parameter, a sixth RRC parameter and a transform precoder in acase that the first RRC parameter indicates codebook and the second RRCparameter indicates that the transform precoding indicator field isincluded in the DCI format.